You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Adrian Herscu <bm...@fastmail.fm> on 2006/02/24 18:35:04 UTC

[m2] m2eclipse error: Build path contains duplicate entry

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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: [m2] m2eclipse error: Build path contains duplicate entry

Posted by Kathryn Huxtable <kh...@ku.edu>.
Ignore that. I responded to the wrong message. ("What a maroon!") -K


On 2/24/06 5:00 PM, "Kathryn Huxtable" <kh...@ku.edu> wrote:

> I thought this had been done long since. -K
> 
> 
> On 2/24/06 4:06 PM, "Kathryn Huxtable" <kh...@ku.edu> wrote:
> 
>> Yes, that's what I do. It means I don't use the eclipse:eclipse goal
>> anymore.
>> 
>> But I prefer to use External tools to build my projects using the external
>> Maven rather than the embedded version. It will never keep up with the
>> released versions and the embedder still doesn't process settings.xml, which
>> is lame.
>> 
>> (Not that I'm opinionated or anything. ;-))
>> 
>> -K
>> 
>> --
>> Kathryn Huxtable
>> Middleware Architect
>> Core Middleware
>> Information Technology, a division of Information Services
>> The University of Kansas
>> 
>> On 2/24/06 3:55 PM, "Lee Meador" <le...@leemeador.com> wrote:
>> 
>>> 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 <kh...@ku.edu> 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" <bm...@fastmail.fm> 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: users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>> 
>>>> 
>>>> --
>>>> Kathryn Huxtable
>>>> Middleware Architect
>>>> Core Middleware
>>>> Information Technology, a division of Information Services
>>>> The University of Kansas
>>>> 
>>>> 
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>> 
>>>> 
>>> 
>>> 
>>> --
>>> -- Lee Meador
>>> Sent from gmail. My real email address is lee@leemeador.com
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>> 
> 
> --
> Kathryn Huxtable
> Middleware Architect
> Core Middleware
> Information Technology, a division of Information Services
> The University of Kansas
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 

--
Kathryn Huxtable
Middleware Architect
Core Middleware
Information Technology, a division of Information Services
The University of Kansas


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: [m2] m2eclipse error: Build path contains duplicate entry

Posted by Kathryn Huxtable <kh...@ku.edu>.
I thought this had been done long since. -K


On 2/24/06 4:06 PM, "Kathryn Huxtable" <kh...@ku.edu> wrote:

> Yes, that's what I do. It means I don't use the eclipse:eclipse goal
> anymore.
> 
> But I prefer to use External tools to build my projects using the external
> Maven rather than the embedded version. It will never keep up with the
> released versions and the embedder still doesn't process settings.xml, which
> is lame.
> 
> (Not that I'm opinionated or anything. ;-))
> 
> -K
> 
> --
> Kathryn Huxtable
> Middleware Architect
> Core Middleware
> Information Technology, a division of Information Services
> The University of Kansas
> 
> On 2/24/06 3:55 PM, "Lee Meador" <le...@leemeador.com> wrote:
> 
>> 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 <kh...@ku.edu> 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" <bm...@fastmail.fm> 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: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>> 
>>> 
>>> --
>>> Kathryn Huxtable
>>> Middleware Architect
>>> Core Middleware
>>> Information Technology, a division of Information Services
>>> The University of Kansas
>>> 
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>> 
>>> 
>> 
>> 
>> --
>> -- Lee Meador
>> Sent from gmail. My real email address is lee@leemeador.com
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 

--
Kathryn Huxtable
Middleware Architect
Core Middleware
Information Technology, a division of Information Services
The University of Kansas


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: [m2] m2eclipse error: Build path contains duplicate entry

Posted by Kathryn Huxtable <kh...@ku.edu>.
Yes, that's what I do. It means I don't use the eclipse:eclipse goal
anymore.

But I prefer to use External tools to build my projects using the external
Maven rather than the embedded version. It will never keep up with the
released versions and the embedder still doesn't process settings.xml, which
is lame.

(Not that I'm opinionated or anything. ;-))

-K

--
Kathryn Huxtable
Middleware Architect
Core Middleware
Information Technology, a division of Information Services
The University of Kansas

On 2/24/06 3:55 PM, "Lee Meador" <le...@leemeador.com> wrote:

> 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 <kh...@ku.edu> 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" <bm...@fastmail.fm> 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: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>> 
>> 
>> --
>> Kathryn Huxtable
>> Middleware Architect
>> Core Middleware
>> Information Technology, a division of Information Services
>> The University of Kansas
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>> 
>> 
> 
> 
> --
> -- Lee Meador
> Sent from gmail. My real email address is lee@leemeador.com


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: [m2] m2eclipse error: Build path contains duplicate entry

Posted by Lee Meador <le...@leemeador.com>.
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 <kh...@ku.edu> 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" <bm...@fastmail.fm> 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: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
>
> --
> Kathryn Huxtable
> Middleware Architect
> Core Middleware
> Information Technology, a division of Information Services
> The University of Kansas
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


--
-- Lee Meador
Sent from gmail. My real email address is lee@leemeador.com

Re: [m2] m2eclipse error: Build path contains duplicate entry

Posted by Kathryn Huxtable <kh...@ku.edu>.
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" <bm...@fastmail.fm> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 

--
Kathryn Huxtable
Middleware Architect
Core Middleware
Information Technology, a division of Information Services
The University of Kansas


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org