[ http://jira.codehaus.org/browse/MNGECLIPSE-105?page=comments#action_68926 ]
Eugene Kuleshov commented on MNGECLIPSE-105: -------------------------------------------- >From http://blogs.unixage.com/blojsom/blog/adam.kruszewski/?month=5&year=2006 I have hacked a little eclipse plugin to do the dirty work for me, and by "dirty work" I mean linking maven resolved dependencies directly into "src/main/webapp/WEB-INF/lib", which results in double classpath entries in project but at last WTP publish the application with all the libraries. Now I can use maven within Eclipse for every project type I could dream of. If you want to obtain the plugin just point the update manager to http://adam.kruszewski.name/eclipse/, it contributes a property page for every project so you can tune it for your needs (the sources are also available but they are not elegant nor pretty -- you ware warned!) http://adam.kruszewski.name/eclipse/libcopy-src.zip > 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 > Assignee: Eugene Kuleshov > Attachments: mngeclipse-test.zip > > > 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
