maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Elliot (JIRA)" <>
Subject [jira] Commented: (MNGECLIPSE-105) Add maven-managed dependencies as project J2EE Module Dependencies
Date Wed, 16 Aug 2006 22:06:49 GMT
    [ ] 
Robert Elliot commented on MNGECLIPSE-105:

I've been stepping through the WTP code, and have as a result raised this improvement request:

I wonder if someone who is much more familiar with the Eclipse extensibility framework could
have a look and see whether there is anything that can be done without an alteration to WTP.
 Questions I immediately have are:

* What happens if two plugins use the org.eclipse.wst.server.core.moduleFactories extension
point, both declaring they are for the same type of project?  Is there any way for a plugin
to specify "use me, not that other one"?

* Can the Maven plugin use this extension point without making the whole plugin dependent
on the WTP project at runtime?  As obviously this extension point would only get used if you
had already installed WTP.

I'm afraid I'm very green when it comes to the Eclipse plugin framework.

> Add maven-managed dependencies as project J2EE Module Dependencies
> ------------------------------------------------------------------
>                 Key: MNGECLIPSE-105
>                 URL:
>             Project: Maven 2.x Extension for Eclipse
>          Issue Type: Wish
>          Components: Dependency Resolver
>    Affects 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
>         Attachments:
> 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:
For more information on JIRA, see:


View raw message