[ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=comments#action_65481 ]
Dimitry Voytenko commented on MNGECLIPSE-59: -------------------------------------------- There's one outstanding issue here though. It doesn't block the progress on this item, but it'll be very nice to have. Currently m2eclipse resolves artifacts in the repository via local file system paths. I.e. inside of the "Maven2 Dependencies" there're entries such as "C:/Documents and Settings/USER/.m2/repository/group/artifact/../x.jar". This prevents other plugins from referring to such entries in the sharable manner. For instance, we're using Sysdeo, which can be setup to start Tomcat's application with the subset of jar files or projects resolved via Maven2. But it's not possible to share this information b/c every user has different home. The solution sould be to have m2eclipse define classpath variable (e.g. M2_REPO or such) and resolve all artifacts via such variable. In the example above it'd be "M2_REPO/group/artifact/../x.jar". Such entries can be shared w/o problems. FYI: Otherwise Sysdeo (http://www.sysdeo.com/eclipse/tomcatplugin) is quite easy to setup to work with Maven2Eclipse plugin. However the current release version has some issues for this to work properly in case of project dependencies (jar files should be fine). I submitted a patch to the Sysdeo team that should fix the issue. > 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
