[jbosstools-issues] [JBoss JIRA] (JBIDE-12815) Create a JBoss Tools Orbit

[Mickael Istria (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-12815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725247#comment-12725247 ] 

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.orbit.releng/maps/?root=Tools_Project

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.
                
> Create a JBoss Tools Orbit
> --------------------------
>
>                 Key: JBIDE-12815
>                 URL: https://issues.jboss.org/browse/JBIDE-12815
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: Build/Releng, UpStream
>            Reporter: Mickael Istria
>            Assignee: Paul Richardson
>
> Since all JBoss Eclipse-based project probably share some needs for usual libraries, we should create a JBoss Tools Orbit project in which one we would provide those 3rd-party dependencies packaged as OSGi Bundle in a p2 repository.
> In a first time, we could simply create some OSGi "wrappers" around those jars.

--
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