[
https://jira.jboss.org/jira/browse/JBIDE-3874?page=com.atlassian.jira.plu...
]
Eugene Kuleshov commented on JBIDE-3874:
----------------------------------------
Max, you can certainly try the maven facet like that and maybe even contribute it back to
m2eclipse, though I don't have complete understanding how such facet is going to
work.
As far as I understand, facets should not be creating resources (including pom.xml), so it
is job for your custom wizards. Then after those resources are created you can call
m2eclipse API to enable Maven support on the newly created project. It is all in the
IProjectConfigurationManager that you can get using
MavenPlugin.getProjectConfigurationManager() call. You can use
updateProjectConfiguration(..) or createSimpleProject(..) calls to update or create
project with Maven support enabled, those call will delegate to the configuration
framework where your custom configurator could kick in. I can provide you more pointers
how these api calls are used if you like.
Maven integration
-----------------
Key: JBIDE-3874
URL:
https://jira.jboss.org/jira/browse/JBIDE-3874
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: common
Affects Versions: 3.0.0.GA
Reporter: Max Rydahl Andersen
Priority: Critical
Fix For: 3.1.0
It is time to make sure our stuff works well with Maven, at least to the extent that the
underline runtimes support it.
First shot would be to add an adapter that allows m2eclipse controlled projects to
activate the seam features.
That would allow us still to bundle JBoss Tools without any dependencies to m2eclipse
which still seem to drag in non-compatible plugins which we need to look into before tying
us to m2eclipse.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira