[
https://issues.jboss.org/browse/JBDS-3071?page=com.atlassian.jira.plugin....
]
Denis Golovin commented on JBDS-3071:
-------------------------------------
Sources were in JBDS even before we migrated from SVN to Git, so it doesn't look like
the reason for growning unless we added a lots of stuff in sources between two releases.
Look at
https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/categ... and
hit blame button, sources were originally in svn.
Looks like Mickael is right we need two repos. But I think those repos should not contain
the same artifacts, the should compliment each other and be published as composite.
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
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)