[
https://issues.jboss.org/browse/JBDS-3087?page=com.atlassian.jira.plugin....
]
Mickael Istria commented on JBDS-3087:
--------------------------------------
Need to check, but it seems to me that the p2-installer from repo linked above creates
multiplatform distributions.
Having spent some time in the past with the IzPack installer, I find it very difficult to
maintain. It's really an old piece of code relying on a technology that no-one seems
to support anymore, and on technologies that are not the most comfortable for our team
(Swing, Ant...). Migrating to newer IzPack is not trivial and require a big amount of
work.
But I agree that this change doesn't require such a migration to a new installer
technology, I'm just taking this jira as an opportunity to tell how much I dislike
IzPack 4.
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)