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

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-12815:
---------------------------------------------

I've finally gotten around to publish my README.md PR at https://github.com/nickboldt/jbosstools-locus/pull/1

This is/was very much based on what is found on Orbit docs about how to do these bundles.

In doing so i've found some discrepencies compared to Orbit we'll need to react to.

1) we are adding jar's inside a bundle instead of using the actual real jar with updated manifest.mf - and advantage/disadvantage to this ? 

2) fest contains multiple jar's incl. javadoc jar - that seems wrong. Why is it not one bundle per jar ?

3) Required execution environment is set to java 6 - is that true for all ?


                
> 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, locus
>            Reporter: Mickael Istria
>            Assignee: Max Rydahl Andersen
>             Fix For: 4.1.0.Beta1
>
>
> 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