[
https://jira.jboss.org/jira/browse/JBIDE-3874?page=com.atlassian.jira.plu...
]
Eugene Kuleshov commented on JBIDE-3874:
----------------------------------------
Max, I would leave the implementation details for "update project configuration
action" out (you will have to go to the m2eclipse mailing list to get the recent
updates). From the user point of view this action should bring Eclipse project
configuration up to the level with pom.xml, e.g. when pom.xml been changed the Eclipse
project configuration may need to be updated.
But you are correct that the same mechanisms are used by the Maven project import wizard
(including checkout from version control and project materialization based on the Maven
coordinates).
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
Assignee: Snjezana Peco
Priority: Critical
Fix For: 3.1.0.M2
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