[
https://jira.jboss.org/jira/browse/JBIDE-3874?page=com.atlassian.jira.plu...
]
Eugene Kuleshov commented on JBIDE-3874:
----------------------------------------
Snjezana, the m2eclipse currently does not support the custom wizards. However you can
create an appropriate pom.xml for the project created by your wizard and then call
m2eclipse API to configure it for Maven support, so it will take care of adding builders,
natures as well as other facets. Also, if you may not be able to use multiple classpath
containers configured by some facets together with Maven integration (because classpath is
managed by Maven and those classes need to be in the pom.xml, so one can build project
from the command line).
Please also note that creating new project is not the only scenario when you need to
configure project. We have list of use cases on the wiki page for configuration framework.
For example, one could try to import an existing Maven project from local file system or
checkout from the version control and in this case you will have to plug into the project
configuration framework, so m2eclipse will delegate to your custom project configurator to
enable functionality specific to jboss tools.
I should also say that currently the faceted framework is only supported in Eclipse
configuration that has the WTP, but there is configurations that may not have WTP pieces
(and may not even require JDT), so we had to make the project configuration framework in
m2eclipse more generic. So, Maven support is somewhat orthogonal to facets.
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