Opened 4 years ago
Closed 4 years ago
#2064 closed task (fixed)
Investigate if fx:deploy task can preserve jar hierarchies
| Reported by: | Zlatin Balevsky | Owned by: | psi |
|---|---|---|---|
| Priority: | minor | Milestone: | soon |
| Component: | installer | Version: | 0.9.31 |
| Keywords: | Cc: | ||
| Parent Tickets: | #2063 | Sensitive: | no |
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 4 years ago by
| Owner: | changed from Zlatin Balevsky to psi |
|---|---|
| Status: | new → assigned |
| Version: | → 0.9.31 |
comment:2 Changed 4 years ago by
| Component: | package/other → installer |
|---|
comment:3 Changed 4 years ago by
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 4 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Psi has discovered that hierarchies are preserved.
Alternative: IzPack? 5 see #1864