Hello,
I have a Java utility project and a web project which depends on it (I added
the utility in the J2EE module dependencies and marked the utility's jars as
exported in its build path).
I then got a warning saying that:
Classpath entry /Utils/lib/commons-configuration-1.4.jar will not be
exported or published. Runtime ClassNotFoundExceptions may result.
I went on and used the quick fix to fix this warning (following Larry
Isaacs' advice).
I now get the following error:
Build path contains duplicate entry: 'D:work/eclipse
workspaces/ws4/Utils/lib/commons-configuration-1.4.jar' for project 'Utils'
There isn't enough info to tell what specifically is leading to this.
You might check the contents of the .classpath file in the Utils project
to see if there is actual duplication for this jar.
Cheers,
Larry
zohar wrote:
> Hello,
> I have a Java utility project and a web project which depends on it (I
> added the utility in the J2EE module dependencies and marked the
> utility's jars as exported in its build path).
> I then got a warning saying that:
>
> Classpath entry /Utils/lib/commons-configuration-1.4.jar will not be
> exported or published. Runtime ClassNotFoundExceptions may result.
>
> I went on and used the quick fix to fix this warning (following Larry
> Isaacs' advice).
> I now get the following error:
>
> Build path contains duplicate entry: 'D:work/eclipse
> workspaces/ws4/Utils/lib/commons-configuration-1.4.jar' for project 'Utils'
>
> Why is that?
>
>
>
>
What I just noticed is that after I use the quick fix, I see mutiple EAR
libraries added to the project's build path (see attached screenshot).
"zohar" <david_fire4@hotmail.com> wrote in message
news:fel63c$ma1$1@build.eclipse.org...
> Hello,
> I have a Java utility project and a web project which depends on it (I
> added the utility in the J2EE module dependencies and marked the utility's
> jars as exported in its build path).
> I then got a warning saying that:
>
> Classpath entry /Utils/lib/commons-configuration-1.4.jar will not be
> exported or published. Runtime ClassNotFoundExceptions may result.
>
> I went on and used the quick fix to fix this warning (following Larry
> Isaacs' advice).
> I now get the following error:
>
> Build path contains duplicate entry: 'D:work/eclipse
> workspaces/ws4/Utils/lib/commons-configuration-1.4.jar' for project
> 'Utils'
>
> Why is that?
>
>
>
>
------=_NextPart_000_004A_01C80C1F.15A9D3F0
Content-Type: image/jpeg;
name="buildpath.JPG"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="buildpath.JPG"
That quick fix is going to add an attribute to the library classpath entry
for commons-configuration-1.4.jar. It should not be adding/removing other
entries to/from the classpath (if you do see that type of behavior, please
open a bug).
The fact that commons-configuration-1.4.jar is resolved by the EAR Libraries
cp container also indicates that you have added this library as a J2EE
module dependency via the EAR.
-Rob
"zohar" <david_fire4@hotmail.com> wrote in message
news:fel9uf$107$1@build.eclipse.org...
> What I just noticed is that after I use the quick fix, I see mutiple EAR
> libraries added to the project's build path (see attached screenshot).
>
> "zohar" <david_fire4@hotmail.com> wrote in message
> news:fel63c$ma1$1@build.eclipse.org...
>> Hello,
>> I have a Java utility project and a web project which depends on it (I
>> added the utility in the J2EE module dependencies and marked the
>> utility's
>> jars as exported in its build path).
>> I then got a warning saying that:
>>
>> Classpath entry /Utils/lib/commons-configuration-1.4.jar will not be
>> exported or published. Runtime ClassNotFoundExceptions may result.
>>
>> I went on and used the quick fix to fix this warning (following Larry
>> Isaacs' advice).
>> I now get the following error:
>>
>> Build path contains duplicate entry: 'D:work/eclipse
>> workspaces/ws4/Utils/lib/commons-configuration-1.4.jar' for project
>> 'Utils'
>>
>> Why is that?
>>
>>
>>
>>