[EMAIL PROTECTED] wrote:
Igor Fedorenko <[EMAIL PROTECTED]> wrote on 18/06/2008 00:06:00:
[EMAIL PROTECTED] wrote:
Igor Fedorenko <[EMAIL PROTECTED]> wrote on 16/06/2008 11:43:31:
Maven projects with packaging=war will be automatically configured as
Dynamic Web WTP project during project import or update configuration
action. All relevant project dependencies will be added to WTP J2EE
Module Dependencies (and removed from Maven Dependencies) and J2EE
Module Dependencies and Maven Dependencies will be automatically
updated
as projects dependencies change.
There is still some bugs/limitations in this area, but this mostly
works
;-) You may want to try to create/import WAR project in WTP 2.0.x and
see how changes to dependencies in POM get reflected in J2EE Module
Dependencies.
Ok, so in essence you are doing the same job as the
maven-eclipse-plugin,
in that you read the pom, and generate the .project, .classpath,
.settings
folder and any other eclipse related meta data.
Is that essentially correct?
Yes, this is correct, except m2eclipse uses public APIs to manipulate
eclipse metadata and provides real-time synchronization of Eclipse
metadata where feasible/practical.
I've seen in the console the m2eclipse using the eclipse:m2eclipse mojo,
which uses the same config information.
So, what is the relationship between your plugin and the maven plugin:
maven-eclipse-plugin:m2eclipse?
I think Eugene already explained on another thread that m2eclipse can be
configured to execute arbitrary maven plugins during project
import/configuration. And although I do not completely understand the
reasons, by default m2eclipse executes m-e-p:eclipse and m-e-p:m2eclipse
goals if m-e-p configuration is present in the pom. These goals have
lowest priority among project configuration steps, and most/all of the
metadata they create will be overwritten.
--
Regards,
Igor
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
