You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Daniel Fern?ndez (JIRA)" <ji...@codehaus.org> on 2006/04/24 18:18:19 UTC
[jira] Created: (MNGECLIPSE-105) Add maven-managed dependencies as
project J2EE Module Dependencies
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
[jira] Updated: (MNGECLIPSE-105) Add maven-managed dependencies as
project J2EE Module Dependencies
Posted by "Daniel Fern?ndez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-105?page=all ]
Daniel Fernández updated MNGECLIPSE-105:
----------------------------------------
Attachment: mngeclipse-test.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
[jira] Commented: (MNGECLIPSE-105) Add maven-managed dependencies
as project J2EE Module Dependencies
Posted by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MNGECLIPSE-105) Add maven-managed dependencies as
project J2EE Module Dependencies
Posted by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-105?page=all ]
Eugene Kuleshov updated MNGECLIPSE-105:
---------------------------------------
Assignee: (was: Eugene Kuleshov)
> 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
> 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: 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
[jira] Commented: (MNGECLIPSE-105) Add maven-managed dependencies
as project J2EE Module Dependencies
Posted by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-105?page=comments#action_64059 ]
Eugene Kuleshov commented on MNGECLIPSE-105:
--------------------------------------------
Please attach an example project that we can use for testing.
I also suspect that this will be very different for WTP 1.5, since they have changed these settings.
> 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
>
>
> 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
[jira] Commented: (MNGECLIPSE-105) Add maven-managed dependencies
as project J2EE Module Dependencies
Posted by "Robert Elliot (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-105?page=comments#action_72466 ]
Robert Elliot commented on MNGECLIPSE-105:
------------------------------------------
Has anyone made any attempt at a more elegant solution? I'm trying to work out whether the org.eclipse.wst.server.core.publishTasks extension point might be a viable way to get in and tell the publish operation to include the appropriate jars/projects from the Maven2 library. Unfortunately I can't check WTP out for some reason.
> 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
> 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: 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
[jira] Commented: (MNGECLIPSE-105) Add maven-managed dependencies
as project J2EE Module Dependencies
Posted by "Robert Elliot (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-105?page=comments#action_72511 ]
Robert Elliot commented on MNGECLIPSE-105:
------------------------------------------
I've been stepping through the WTP code, and have as a result raised this improvement request:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=154165
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: http://jira.codehaus.org/browse/MNGECLIPSE-105
> 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: 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
[jira] Commented: (MNGECLIPSE-105) Add maven-managed dependencies
as project J2EE Module Dependencies
Posted by "Borut Bolcina (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNGECLIPSE-105?page=comments#action_64494 ]
Borut Bolcina commented on MNGECLIPSE-105:
------------------------------------------
Hello,
I am using Eclipse 3.2 RC2 with the latest (also RC2) Callisto update site modules (Web Standard Tools Version: 1.5.0.v200604030005-eYe38P_OHPq8Dcd) and Maven plugin 0.0.6
and having the same issue.
Resolving this request would really boost dev cycle.
Regards,
Borut
> 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