Add maven-managed dependencies as project J2EE Module Dependencies
------------------------------------------------------------------
Key: MNGECLIPSE-105
URL: http://jira.codehaus.org/browse/MNGECLIPSE-105
Project: Maven 2.x Extension for Eclipse
Type: Wish
Components: Dependency Resolver
Versions: 0.0.5
Environment: Eclipse 3.1.2 with WTP 1.0, using Tomcat 5.5 for running webapp
projects. Maven 2.x Extension for Eclipse
Reporter: Daniel Fernández
Assigned to: Eugene Kuleshov
When creating a WTP's Dynamic Web project with eclipse, following a maven2
directory structure and creating a pom.xml file for it using the Maven 2.x
Extension for Eclipse, everything works ok with dependencies as these are
added to the project build path (under the "Maven 2 Dependencies" folder) as
soon as they are added to the pom.xml
But, when this project is being run in a Tomcat Server from eclipse, these
dependencies are not being added to the WEB-INF/lib directory. This could be
done by adding, for each newly added dependency and its transitive dependencies
(not having scope "provided" or "test") an entry into the
".settings/.component" file like these:
<dependent-module deploy-path="/WEB-INF/lib"
handle="module:/classpath/var/M2_REPO/commons-collections/commons-collections/2.1/commons-collections-2.1.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
(this one was written by the maven-eclipse-plugin, which creates these entries)
This way webapps created from eclipse and managed by maven could be
automatically run in Tomcat from Eclipse.
Regards,
Daniel.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
