Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JBIDE-15969: Remove useless m2e extensions from TP #31

Merged
merged 1 commit into from
Dec 17, 2013
Merged

JBIDE-15969: Remove useless m2e extensions from TP #31

merged 1 commit into from
Dec 17, 2013

Conversation

mickaelistria
Copy link
Contributor

No description provided.

@nickboldt
Copy link
Member

Just make sure these are not needed to build JBDS, or else we'll need to ensure they're in the Central TP and that we reference the Central TP when building JBDS.

@mickaelistria
Copy link
Contributor Author

I verified and those features are not part of jbds feature.

If they're necessary for discovery sites, we'll move them there.

Mickael Istria
Eclipse developer at JBoss, by Red Hat http://www.jboss.org/tools
My blog http://mickaelistria.wordpress.com - My Tweets
http://twitter.com/mickaelistria

@nickboldt
Copy link
Member

Looks like the only m2e-* in Central TP is m2e-wro4j.

https://github.com/jbosstools/jbosstools-discovery/blob/master/jbtcentraltarget/multiple/jbtcentral-multiple.target#L26

However, there are others in here, which would need to move from the JBT TP to the Central TP to be resolved:

https://github.com/jbosstools/jbosstools-discovery/blob/master/jbosstools/org.jboss.tools.central.discovery/plugin.xml :

        <iu id="org.eclipse.m2e.wtp.jaxrs.feature"/>
        <iu id="org.eclipse.m2e.wtp.jsf.feature"/>
        <iu id="org.jboss.tools.maven.jbosspackaging.feature"/>
        <iu id="org.eclipse.m2e.feature"/>
        <iu id="org.eclipse.m2e.wtp.feature"/>
        <iu id="org.eclipse.m2e.wtp.jpa.feature"/>
        <iu id="org.jboss.tools.maven.apt.feature"/>
        <iu id="org.jboss.tools.m2e.wro4j.feature"/>

@mickaelistria
Copy link
Contributor Author

m2e-wtp stays in the "core" target platfrom, and m2e.wro4j is already in. So it looks like in this list, only maven.apt has to be added to the Central target platform. I'll make another PR for that.

@mickaelistria
Copy link
Contributor Author

See also related PR for jbosstools-discovery jbosstools/jbosstools-discovery#126

@nickboldt
Copy link
Member

What about jaxrs, jsf, jpa?

@mickaelistria
Copy link
Contributor Author

@nickboldt
Copy link
Member

Right, but i thought you were looking to move these to Central. If they're needed by the base JBT/JBDS install, though, I suppose they need to stay where they are. Anyway, disco #126 is applied.

@mickaelistria
Copy link
Contributor Author

I did not check whether these ius are necessary to install from JBT site or not. If they're not necessary to install JBT, we might be able to move them to Central as well.

@mickaelistria
Copy link
Contributor Author

@mickaelistria mickaelistria merged commit 0848a1a into jbosstools:4.40.x Dec 17, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants