What you do is remove the classpath entries that AREN'T under "maven dependencies". I suppose you could say that the ones under "maven dependencies"are the original entries now and the ones you used to use are the duplicates.
-- Lee On 2/24/06, Kathryn Huxtable <[EMAIL PROTECTED]> wrote: > > Correct. With the M2ECLIPSE eclipse plugin, you either use it to manage > your > dependencies from your pom.xml, or you don't enable the Maven2 nature and > use maven to create your .classpath files. > > The container in your classpath is getting the dependencies from the POM. > It's actually pretty clever. > > -K > > > On 2/24/06 11:35 AM, "Adrian Herscu" <[EMAIL PROTECTED]> wrote: > > > Hi all, > > > > After enabling an existing M2 project the Eclipse builder complains > > about duplicate path entries. > > > > I looked into the Project-properties/JavaBuildPath/Libraries and the > > problem is that dependency paths declared in the pom.xml are declared > > again under some "Maven 2 Dependencies". > > > > The only options to fix this kind of build errors are > > - delete the "Maven 2 Dependencies" > > - disable Maven 2 support > > > > Adrian. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > -- > Kathryn Huxtable > Middleware Architect > Core Middleware > Information Technology, a division of Information Services > The University of Kansas > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- -- Lee Meador Sent from gmail. My real email address is [EMAIL PROTECTED]
