Guillaume,
Please note that 'Enable Dependency Management' action currently does
NOT convert your custom project configuration into corresponding
configuration for Maven plugins in pom.xml. So, if your web project is
not using Maven's conventions you have to either fix configuration for
Maven plugins manually or change your project layout to match Maven
conventions (see documentation for corresponding plugins, e.g.
maven-war-plugin). In other words your project should be buildable with
Maven from the command line, e.g. using command "mvn package".
You may want to vote on the following issues:
* http://jira.codehaus.org/browse/MNGECLIPSE-781
* http://jira.codehaus.org/browse/MNGECLIPSE-1191
regards,
Eugene
Guillaume Boucherie wrote:
I have a problem with the plugin when I try to convert a project to maven.
Let me explain the different steps :
1. First I create a normal (I mean without maven) dynamic web
project, with java sources in src and webapp directory in WebContent
2. Then I activate maven with the 'Enable Dependency Management' option
3. And by default m2eclipse think the WEB-INF/web.xml is located in
the src/main/webapp directory so I configure the maven-war-plugin with
property warSourceDirectory set to ${basedir}/WebContent
4. Then I force the plugin to update the project configuration by
selecting the 'Update Project Configuration'
The problem is that m2eclipse don't use the WebContent directory as
webapp, it first resolved the basedir property.
So if your project is located in 'D:\workspace\project', m2eclipse
will use 'workspace/project/WebContent' as webapp !!!
Does anybody face the same problem ?
Thanks
CletteBou
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
