[jbosstools-issues] [JBoss JIRA] (JBIDE-15969) Investigate removing some m2e extensions for TP

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-15969:
----------------------------------------

[~fbricon] Do you know whether these ius are necessary to build/install JBT? If not, we can move them to Central as well.
{code}
<unit id="org.eclipse.m2e.wtp.jaxrs.feature.feature.group" version="1.1.0.20130821-1331"/>
<unit id="org.eclipse.m2e.wtp.jpa.feature.feature.group" version="1.1.0.e43-20130821-1332"/>
<unit id="org.eclipse.m2e.wtp.jsf.feature.feature.group" version="1.1.0.20130821-1331"/
{code}
                
> Investigate removing some m2e extensions for TP
> -----------------------------------------------
>
>                 Key: JBIDE-15969
>                 URL: https://issues.jboss.org/browse/JBIDE-15969
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: target-platform
>    Affects Versions: 4.1.1.CR1, 4.2.0.Alpha1
>            Reporter: Mickael Istria
>            Assignee: Mickael Istria
>            Priority: Minor
>             Fix For: 4.2.0.Alpha2
>
>
> It looks like m2e-wro4j is not used at all in JBoss Tools (only referenced in Central).
> It also appears that other m2e extensions (maven.apt and m2e.jdt) are not necessary to build JBT, and are only made available by default in JBDS installer and on Central.
> So I suggest the following changes:
> * Remove the 3 maven extensions (m2e.wro4j, maven.apt, m2e.jdt) from the JBT target-platform, and keep them only in Central
> * Remove m2e.wro4j from JBDS TP (as it's not part of installer)

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