[
https://issues.jboss.org/browse/JBIDE-15340?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-15340:
------------------------------------
They've been there since day one, so that you can install anything from the Locus site
w/o having to add additional sites to Eclipse to resolve deps.
Please clarify how having the Locus site automatically add references to the latest JBT TP
and JBT Aggregate sites causes a *cyclic* dependency, if nothing in JBT depends on Locus?
Perhaps we should instead be referring to these 4 sites?
https://github.com/jbosstools/jbosstools-locus/blob/master/target-platfor...
(Orbit R20130517)
https://github.com/jbosstools/jbosstools-locus/blob/master/target-platfor...
(Juno SR2)
https://github.com/jbosstools/jbosstools-locus/blob/master/target-platfor...
(SpringIDE 3.2)
https://github.com/jbosstools/jbosstools-locus/blob/master/target-platfor...
(Eclipse Gemini Management 2.0.0 / osgi.jmx)
Remove site references from Locus site
--------------------------------------
Key: JBIDE-15340
URL:
https://issues.jboss.org/browse/JBIDE-15340
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: locus
Reporter: Rob Cernich
Assignee: Nick Boldt
Priority: Blocker
Fix For: 1.1.0-LOCUS
The Locus p2 repo/update site should not include references to other update sites.
Currently it includes references to other sites, e.g.
http://download.jboss.org/jbosstools/updates/development/juno/
--
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