[ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=comments#action_64234 ]
Dimitry Voytenko commented on MNGECLIPSE-59: -------------------------------------------- I agree. These are two different issues: 1) WebTools is actually not a classpath container, they use the regular project dependency. The J2EE module dependency is stored in the ".component" file. Modules in this file are synchronized with the project's classpath when they're added. This synchronization operation is what actually fails b/c classpath contains the dependent project already (provided by Maven2 classpath container). This could be probably resolved by having Maven2 plugin to automatically extend ".component" content for the non "provided" dependencies (altough I don't know if there's API or extension points there to do that). 2) PDE plugin dependency. They are provided by the "Plugin Dependencies" classpath container. So they would be in conflict with Maven2 classpath container. I understand that PDE container is instantiated based on the "Require-Bundle" property from the plugin's MANIFEST.MF. This manifest is essential for PDE system to work properly (actually for OSGI). I don't think there's an obvious way to avoid a conflict b/w these two containers (PDE and Maven2), b/c it's not likely one can disable another container. If there're no objections, I'll open two new issues in addition to this one: one for webtools support and one for pde support. > Allow artifact resolution from workspace projects > ------------------------------------------------- > > Key: MNGECLIPSE-59 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-59 > Project: Maven 2.x Extension for Eclipse > Type: New Feature > Components: Dependency Resolver > Versions: 0.0.4 > Reporter: Leonardo Quijano Vincenzi > Assignee: Eugene Kuleshov > Fix For: 1.0.0 > Attachments: ArtifactResolver-try3.patch, > EclipseArtifactResolver-corrected.patch, EclipseArtifactResolver.patch, > maven-embedder-2.1-SNAPSHOT-dep.jar > > > Provide artifact resolution from workspace projects, which override the same > artifact from the local or remote repositories. This would allow to work with > dependant Eclipse projects without specifying the Eclipse dependency manually. > The workspace artifact resolution would have to be specified manually, since > several Maven-Enabled projects in the same workspace could have the same > artifact and version Id. Or at least automatic resolution with an optional > override would be nice. > More comments here: > http://jira.codehaus.org/browse/MNGECLIPSE-58 -- 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
