[
https://issues.jboss.org/browse/JBTIS-89?page=com.atlassian.jira.plugin.s...
]
Nick Boldt commented on JBTIS-89:
---------------------------------
Might want to look at what we do in JBT / JBDS.
JBT: aggregate site is built w/ <references> to upstream sites (previously multiple
sites, now really just the TP site) in the site's metadata, so that the single zip (or
site) can be used to resolve all the upstream.
https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat...
JBDS: aggregate site is built using the TP as a baseline (via reference in the pom [1]),
but we don't refer to it in the completed update site; rather, we composite the TP
into the site [2] end users search for updates.
[1]
https://svn.jboss.org/repos/devstudio/trunk/product/pom.xml (see tpc.group and
tpc.version)
[2]
https://devstudio.jboss.com/updates/7.0-development/compositeContent.xml
target platform repo should not contain repository references
-------------------------------------------------------------
Key: JBTIS-89
URL:
https://issues.jboss.org/browse/JBTIS-89
Project: JBoss Tools Integration Stack
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Rob Cernich
Assignee: Paul Leacu
Priority: Critical
I don't see how this repo could be used in a jbds setting when it contains repository
references to jbt repositories. My understanding was that this repo only contained the
extra dependencies for jbt-is. By including these references, if this repo is used in
jbds, all those linked repos will be available too, polluting the pool of available
features/bundles.
--
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