[jbosstools-issues] [JBoss JIRA] (JBIDE-15018) Locus plugins should include actual COMMITTED sources rather than pulling them from upstream (maven central, sourceforge) for each build
Denis Golovin (JIRA)
jira-events at lists.jboss.org
Tue Jul 16 13:50:26 EDT 2013
[ https://issues.jboss.org/browse/JBIDE-15018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790083#comment-12790083 ]
Denis Golovin commented on JBIDE-15018:
---------------------------------------
With this approach it is going to be huge soon, since we are going to add full sources for every new version.
> Locus plugins should include actual COMMITTED sources rather than pulling them from upstream (maven central, sourceforge) for each build
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15018
> URL: https://issues.jboss.org/browse/JBIDE-15018
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, locus, updatesite, upstream
> Affects Versions: 1.0.0-LOCUS
> Reporter: Nick Boldt
> Fix For: 1.0.1-LOCUS
>
>
> Currently, Locus plugins pull content from upstream, then compile locally. Instead, we should actually include sources in Locus so that:
> a) sources are copied/cached
> b) builds are more reproducible / not dependent on upstream sites
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list