[JCRTOOLS-23] Properly create ExportCommand.EXPORT_FILE_NAME for node exports Created: 09/Feb/16 Updated: 29/Mar/22 Resolved: 11/Feb/16 |
|
| Status: | Closed |
| Project: | JCR Tools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Bradley Andersen | Assignee: | Bradley Andersen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Sprint: | Basel 31 |
| Story Points: | 1 |
| Team: |
| Description |
|
In the JCRTOOLS Exporter sub app, the ExportCommand.EXPORT_FILE_NAME is set using a private local method. It should be created as it is elsewhere in the system, using DataTransporter#createExportPath. Please remove ExporterSubApp#getExportFileName and replace this functionality with DataTransporter#createExportPath. |