[
https://issues.jboss.org/browse/JBDS-3087?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-3087:
----------------------------------
"Difficult to maintain" is a fairly subjective phrase. We've been using
izpack 4.3.3 - 4.3.5 since JBDS 4. The handful of commits needed to keep the installer
working hasn't been that onerous - most have been string changes around JDK support
versions and updates to graphics. See
https://github.com/jbdevstudio/jbdevstudio-product/commits/master/installer
Regardless, if we can move to something better, I'm all for that. I'm just not
convinced that izPack is so bad given we've successfully released at least 10 JBDS GA
and maintenance releases (4.0.x, 4.1.x, 5.x, 6.x, 7.0.x, 7.1.x) w/ izPack over the years.
Consider new installer packages
-------------------------------
Key: JBDS-3087
URL:
https://issues.jboss.org/browse/JBDS-3087
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: installer
Affects Versions: 8.0.0.Beta2
Reporter: Nick Boldt
Today we have two installers:
* Stand-alone Installer (504M)
* Installer with EAP (642M)
Both can be used for offline install, but both are large downloads.
When installing JBDS IS offline, a user must download several archives:
* JBDS installer jar (or update site zip)
* JBDS target platform zip
* JBDS IS zip
And, there's no "stub installer for online" which would simply fetch the
content needed to do the install from the update site, making the installer a much smaller
(initial) download footprint.
Therefore Max has suggested that we might want to add two new installers, resulting in
this list:
* Stand-alone Installer (504M)
* Installer with EAP (642M)
* Installer with Integration Stack (~750M)
* Stub Installer (~10M)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)