-
Notifications
You must be signed in to change notification settings - Fork 35
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
Conversation
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. |
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 |
Looks like the only m2e-* in Central TP is m2e-wro4j. However, there are others in here, which would need to move from the JBT TP to the Central TP to be resolved:
|
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. |
See also related PR for jbosstools-discovery jbosstools/jbosstools-discovery#126 |
What about jaxrs, jsf, jpa? |
They're already in Core target-platform: |
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. |
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. |
@nickboldt See https://issues.jboss.org/browse/JBIDE-15969?focusedCommentId=12931739&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12931739 , those features are required for JBT, so thay can't be moved. |
No description provided.