[
https://issues.jboss.org/browse/JBDS-3071?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-3071:
----------------------------------
Built OK after applying a second fix to PR 196:
https://github.com/jbdevstudio/jbdevstudio-product/commit/d59721f13a8182a...
Resulting size reduction: ~43M for installer-standalone , ~30M for installer-eap:
{code:title=http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_master/installer/?C=S;O=A}
jboss-devstudio-8.0.0.Beta3-v20140630-1754-B2249-installer-standalone.jar 30-Jun-2014
14:04 507M
jboss-devstudio-8.0.0.Beta3-v20140630-1754-B2249-installer-eap.jar
30-Jun-2014 14:03 646M
{code}
vs.
{code:title=http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_8.0.luna/installer/?C=S;O=A}
jboss-devstudio-8.0.0.Beta2-v20140617-2058-B166-installer-standalone.jar 17-Jun-2014
17:06 550M
jboss-devstudio-8.0.0.Beta2-v20140617-2058-B166-installer-eap.jar 17-Jun-2014
17:05 676M
{code}
JBDS Installer shouldn't contain source features/plugins
--------------------------------------------------------
Key: JBDS-3071
URL:
https://issues.jboss.org/browse/JBDS-3071
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: installer
Affects Versions: 8.0.0.Beta2
Reporter: Fred Bricon
Assignee: Nick Boldt
Fix For: 8.0.0.Beta3
{quote}
So the basic JBDS installer is 70MB fatter. From my understanding it's because we now
ship a *huge* forge2 runtime (50MB), Tern, the JVM Monitor and probably some other minor
stuff.
Fair enough. But do we *really* need to add all the source features/plugins to the
installer? *If* we're legally bound to provide sources for JBoss plugins, couldn't
we provide them via an other way? (p2 only).
I reckon we could save ~37 MB by not shipping sources in the installer. I know storage is
cheap and d/l speeds are faster but that's not an excuse.
{quote}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)