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

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBIDE-12815 at 4/19/13 12:40 PM:
--------------------------------------------------------------

Hey, if we migrate this to a new project, https://github.com/jbosstools/jbosstools-locus, and fix the namespaces such that s/org.jbosstools/org.jboss.tools/g, do we need all the 1:1 feature wrappers?

* We can add plugins to our TP (features are not needed). 
* We can have our plugins depend on locus plugins, and be installed to an update site, then to a user's Eclipse.
* We can have our features include or depend on locus plugins, and be installed to an update site, then to a user's Eclipse.

* We only need features IFF there's a use case for a user to be installing Mockito or another Locus component *DIRECTLY*, via p2 Install, or JBoss Central.

So, is there a reason to have org.jboss.tools.locus.*.feature features?

Or do we perhaps only need an org.jboss.tools.locus.feature, which contains all the plugins in a single feature, like the way Eclipse Orbit works? We can then look at publishing all the individual plugins to an update site w/o the need for feature wrappers.

Ref: https://bugs.eclipse.org/bugs/show_bug.cgi?id=378338#c21
                
      was (Author: nickboldt):
    Hey, if we migrate this to a new project, https://github.com/jbosstools/jbosstools-locus, and fix the namespaces such that s/org.jbosstools/org.jboss.tools/g, do we need all the 1:1 feature wrappers?

* We can add plugins to our TP (features are not needed). 
* We can have our plugins depend on locus plugins, and be installed to an update site, then to a user's Eclipse.
* We can have our features include or depend on locus plugins, and be installed to an update site, then to a user's Eclipse.

* We only need features IFF there's a use case for a user to be installing Mockito or another Locus component *DIRECTLY*, via p2 Install, or JBoss Central.

So, is there a reason to have org.jboss.tools.locus.*.feature features?

Or do we perhaps only need an org.jboss.tools.locus.feature, which contains all the plugins in a single feature, like the way Eclipse Orbit works? We can then look at publishing all the individual plugins to an update site w/o the need for feature wrappers.

Ref: https://bugs.eclipse.org/bugs/show_bug.cgi?id=378338
                  
> 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: Paul Richardson
>             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