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

Nick Boldt (JIRA) jira-events at lists.jboss.org
Thu Nov 14 16:35:07 EST 2013


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

Nick Boldt edited comment on JBIDE-15969 at 11/14/13 4:34 PM:
--------------------------------------------------------------

[~maxant] I'm already prepared for when we decide to have two different central TPs, but I'm resisting it as long as possible because it's more pain than gain. 

As to where it lives, since we've been told we can serve products from jboss.org (eg., JBoss EAP), surely it's acceptable that the 3rd party stuff in Central can come from http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/kepler/ under the covers [1]?

[1] https://devstudio.jboss.com/updates/7.0-development/central/core/compositeArtifacts.xml 
                
      was (Author: nickboldt):
    Already prepared for when we decide to have two different central TPs, but I'm resisting it as long as possible. As to where it lives, since we've been told we can serve products from jboss.org, surely it's acceptable that the 3rd party stuff in Central can come from http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/kepler/ under the covers?
                  
> 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


More information about the jbosstools-issues mailing list