]
Max Rydahl Andersen commented on JBDS-3087:
-------------------------------------------
[~mickael_istria] the problem with the native p2 installer is that this would triple the
amount of installers we would need.
if that p2-installer can run with pure "java -jar p2installer.jar" then yes that
would be relevant.
btw. you are aware that our current installer does use p2 director to do its install today
so the installer today can actually do what is suggested here. Just need to repackage it
to use remote site instead of bundled one.
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)