[ https://issues.jboss.org/browse/JBIDE-12815?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-12815: ---------------------------------------- They have a repository which is using tags, and they use a map file to get fetch specified version of each bundle, they build it, and then they run some p2 publishers on it: http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.orbit/org.eclipse.o... They use tagged version because they can have several versions of a dependency. I'd rather see the following: * pom.xml * repository ** pom.xml ** category.xml * bundleA ** versionA *** pom.xml *** MANIFEST.MF *** A.jar * bundleB ** versionB *** pom.xml *** MANIFEST.MF *** B.jar ... Parent pom.xml would reference multiple jars in different versions. IMO Orbit tags make it more complicated because they use it for the included bundles, whereas tags should apply to the whole project. Having 2 versions of one bundle in a project does not justify usage of tags. -- 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

[ https://issues.jboss.org/browse/JBIDE-12815?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-12815: --------------------------------------------- ref to mailing list thread on this: http://lists.jboss.org/pipermail/jbosstools-dev/2012-October/006278.html -- 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