[
https://issues.jboss.org/browse/JBIDE-15340?page=com.atlassian.jira.plugi...
]
Rob Cernich commented on JBIDE-15340:
-------------------------------------
I agree with Max that it should be a standalone site with no links (obviously, I created
the issue). If there are dependencies that are external to Locus, I think those should be
resolved as part of the target platform. In these cases, the JBTIS target platform would
include those external dependencies, which would be collected as part of the TP site. In
the case of JBTIS, the associated sites are: JBT core + JBTIS TP. With that, the user
gets everything they need to install from the JBTIS site, thus there is no need for adding
any associate sites to Locus. The onus should be on the consumer of Locus to ensure any
external dependencies are resolved appropriately.
I think this is similar to how Orbit works. I assume (yikes) that Orbit does not add any
references back to the main Eclipse repositories (e.g. Kepler, Juno, etc.).
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