[jbosstools-issues] [JBoss JIRA] (LOCUS-1) Locus plugins should include actual COMMITTED sources rather than pulling them from upstream (maven central, sourceforge) for each build
[
https://issues.jboss.org/browse/LOCUS-1?page=com.atlassian.jira.plugin.sy...
]
Max Rydahl Andersen reassigned LOCUS-1:
---------------------------------------
Project: JBoss Tools Locus (was: Tools (JBoss Tools))
Key: LOCUS-1 (was: JBIDE-15018)
Affects Version/s: 1.0.0
(was: 1.0.0-LOCUS)
Assignee: (was: Mickael Istria)
Component/s: (was: build)
(was: upstream)
(was: updatesite)
(was: locus)
Fix Version/s: 1.1.0
(was: 1.1.0-LOCUS)
Locus plugins should include actual COMMITTED sources rather than
pulling them from upstream (maven central, sourceforge) for each build
----------------------------------------------------------------------------------------------------------------------------------------
Key: LOCUS-1
URL: https://issues.jboss.org/browse/LOCUS-1
Project: JBoss Tools Locus
Issue Type: Bug
Affects Versions: 1.0.0
Reporter: Nick Boldt
Fix For: 1.1.0
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 was sent by Atlassian JIRA
(v6.3.11#6341)