[
https://issues.jboss.org/browse/JBIDE-10871?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-10871:
----------------------------------------
Current layout of jars in modules make it quite difficult to automate fetch and assembly
with Maven.
However, we could think for creating a maven plugin that would look for
fileToFetch.urlfetch files (such as activiation-1.1.jar.urlfetch) containing URL to fetch
files, and that would perform a get on this url to replace fileToFetch.urlFetch by
fileToFetch. OR something better with .artifactGet files that would simply be replaced by
artifacts as they are available in repo.
No trivial solution... And I'm afraid not committing jars will make daily work more
annoying for Koen. As for the build, we will need to download these jars, whether we get
them from SCM or a maven plugin won't have sensible impact on performances.
should forge component include so many jars in SVN?
---------------------------------------------------
Key: JBIDE-10871
URL:
https://issues.jboss.org/browse/JBIDE-10871
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Koen Aers
Fix For: 3.3.0.CR1
https://svn.jboss.org/repos/jbosstools/trunk/forge/plugins/org.jboss.tool...
used to contain over 46M of jars; after the last SVN update, it's still over 20M.
Surely this doesn't need to be in SVN? Couldn't it be fetched during a build, or
cached in a user's ~/.m2/repo ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira