#933 closed enhancement (fixed)
Add support for exporting files to a remote server to the Release exporter plug-in
| Reported by: | Nicklas Nordborg | Owned by: | Nicklas Nordborg |
|---|---|---|---|
| Priority: | major | Milestone: | Reggie v4.10 |
| Component: | net.sf.basedb.reggie | Keywords: | |
| Cc: |
Description
The current implementation of the release exporter plug-in can only save the result files to the BASE file system. We should implement support for saving to an external file server.
Change History (7)
comment:1 by , 7 years ago
comment:2 by , 7 years ago
comment:3 by , 7 years ago
(In [4345]) References #933: Add support for exporting files to a remote server to the Release exporter plug-in
Implemented support in the release exporter plug-in for selecting "local" or "remote" export. The configuration is now a two-step process.
The local export is the same as before. The remote exports requires a selection of a FileServer item. A unique ID is automatically generated. The intention is that this ID should be used on the import side to find the exported files.
comment:4 by , 7 years ago
| Status: | new → assigned |
|---|
comment:5 by , 7 years ago
comment:6 by , 7 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:7 by , 7 years ago
Note:
See TracTickets
for help on using tickets.
(In [4339]) References #933: Add support for exporting files to a remote server to the Release exporter plug-in
Re-factored the
ReleaseExportercode. Introduced a new classOutputLocationwhich abstracts away the file handling from the export code. TheBaseFileOutputLocationis an implementation that save files to the BASE file system.Initial tests indicates that a
FileServer-based implementation should be possible. A bit more testing and error handling is needed.