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

[Max Rydahl Andersen (JIRA)]

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

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

Sounds sensible to not require these in the TP if not required by builds or any tests.

About JBT=JBDS TP then you know my opinion on that ;)
You can keep the source for those the same, but the JBDS must be hosted on devstudio.jboss.com and the day the two will differ (and they will) you should be ok to do the split.
                
> 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