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

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-15969:
------------------------------------

Note that maven.apt, m2e.jdt are not in Central TP at the moment, so removing them from JBT TP would require moving them to Central TP. My previous comment was only about m2e-wro4j, which I added here as part of JBDS-2577:

https://github.com/jbosstools/jbosstools-discovery/pull/101/files#diff-8b437c1a6a011c2cd0f7a0e486a47b2bL22
https://github.com/jbosstools/jbosstools-discovery/pull/102/files#diff-8b437c1a6a011c2cd0f7a0e486a47b2bL22
                
> 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
>            Priority: Minor
>             Fix For: 4.2.0.Alpha1
>
>
> 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