Opened 18 months ago
Closed 18 months ago
#2064 closed task (fixed)
Investigate if fx:deploy task can preserve jar hierarchies
| Reported by: | zab | Owned by: | psi |
|---|---|---|---|
| Priority: | minor | Milestone: | soon |
| Component: | installer | Version: | 0.9.31 |
| Keywords: | Cc: | ||
| Parent Tickets: | #2063 |
Description
In order for the in-network update to work, the jars (and many other files) need to be in a specific hierarchy. The fx:deploy task might be flattening any hierarchies and if it is, it can't be used.
Need to investigate if it is possible to use that task and preserve the file hierarchy.
Subtickets
Change History (4)
comment:1 Changed 18 months ago by zab
- Owner changed from zab to psi
- Status changed from new to assigned
- Version set to 0.9.31
comment:2 Changed 18 months ago by zzz
- Component changed from package/other to installer
comment:3 Changed 18 months ago by zzz
See also: Web start #1222 and desktop file #1928
Note that any IzPack? replacement must also handle the actions currently done in installer/install.xml and installer/resources/postinstall.sh. A scripting solution may be better than the proposal to do OSX-specific things in InstallUpdate?.java.
Also note that one opportunity for reducing the installer size is to pack200 the jars. Was tried for one release long ago in IzPack?, but disabled because pack200 wasn't available in some JVMs. This probably isn't true anymore, especially on a relatively closed environment like OSX.
comment:4 Changed 18 months ago by zab
- Resolution set to fixed
- Status changed from assigned to closed
Psi has discovered that hierarchies are preserved.
Alternative: IzPack? 5 see #1864