[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

Tue Jul 16 17:24:26 EDT 2013

    [ https://issues.jboss.org/browse/JBIDE-15018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790139#comment-12790139 ] 

Nick Boldt commented on JBIDE-15018:
------------------------------------

If we depend on maven artifacts in Maven Central, they will never disappear until the heat death of the universe, but hey. If we want to copy sources and maintain 'em as duplicates in our (ever-growing) repo, so be it. I agree w/ Denis that it's sorta pointless to clone sources of maven artifacts when they'll exist in perpetuity...

But for things we fork, or for which the SVN sources differ from the released version (eg., saxon) it makes sense to have our own reproduceable copy.

> 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
>            Assignee: Mickael Istria
>             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