[jbosstools-issues] [JBoss JIRA] (JBIDE-16757) move m2e.jdt.feature from JBDS TP to Central TP and expose as connector in Central Discovery site?

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-16757:
------------------------------------

Assign to [~fbricon] for comments.
                
> move m2e.jdt.feature from JBDS TP to Central TP and expose as connector in Central Discovery site?
> --------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-16757
>                 URL: https://issues.jboss.org/browse/JBIDE-16757
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: central, discovery
>    Affects Versions: 4.2.0.Beta1
>            Reporter: Nick Boldt
>            Assignee: Fred Bricon
>             Fix For: 4.2.0.Beta2
>
>
> Currently, we include m2e.jdt.feature (an m2e-extension) in the JBDS TP, but not the JBT one. 
> {code:title=https://github.com/jbosstools/jbosstools-target-platforms/blob/4.40.x/jbdevstudio/multiple/jbdevstudio-multiple.target#L111-L114}
>     <!-- NOTE: m2e-extension m2e.jdt.feature is only in JBDS BYOE / installer (unlike maven.jdt.feature, which is part of jbosstools-central and is therefore in BOTH JBT & JBDS update sites) -->
>     <location includeAllPlatforms="false" includeMode="slicer" type="InstallableUnit" includeSource="true">
>       <repository location="http://download.jboss.org/jbosstools/updates/m2e-extensions/m2e-jdt-compiler/"/>
>       <unit id="org.jboss.tools.m2e.jdt.feature.feature.group" version="1.0.1.201209200903"/>
>     </location>
> {code}
> Since this is useful to JBT users and JBDS users alike, we could consider moving this from the JBDS TP into the Central TP and exposing it as a new Central Discovery connector.

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