[ http://jira.codehaus.org/browse/MNGECLIPSE-9?page=comments#action_52328 ]
Eugene Kuleshov commented on MNGECLIPSE-9: ------------------------------------------ What do you think would be the right way to do this? Should we wipe out all the entries that are using M2_REPO variable? Currently you would have to manually remove all jars pointing to M2_REPO variable from the Eclipse build path. > Classpath entries based on M2_REPO interfere with plugin classpath entries > -------------------------------------------------------------------------- > > Key: MNGECLIPSE-9 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-9 > Project: Maven 2.x Plug-in for Eclipse > Type: Wish > Environment: Windows XP, Eclipse 3.1, MyEclipse, local repo, no mirrors, > IBiblio is central repo, plugin version 0.0.3 > Reporter: Lee Meador > Assignee: Eugene Kuleshov > Priority: Minor > > > My projects had originally been set up using mvn eclipse:eclipse so there > were a bunch of M2_REPO based items in the classpath. When I added the > maven2Nature with the menu selection, it added the maven based dependencies > which, of course, duplicated the M2_REPO ones and caused an error. Perhaps > there could be some way to remove the M2_REPO ones that are duplicates of the > ones from the POM. I don't imagine everyone is so meticulous as to keep the > two in sync when doing it by hand. -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
