Re: [m2e-users] Update Project resets my .classpath if local libraries a

[Rafał Krzewski <rafal.krzewski@xxxxxxxxx>]

Tony,

just to clarify, are you using Tycho [1], or are you trying to build a PDE project that has JAR files stored locally?

Cheers,
Rafał

[1] http://eclipse.org/tycho/

On 01/15/2013 01:24 PM, Tonny Madsen wrote:

No. They are only present in MANIFEST.MF (Bundle-ClassPath), .classpath and in build.properties (bin.includes). It is *not* an external dependency, so I don't have anything in the pom.xml.

But... should I?

/Tonny

On Tue, Jan 15, 2013 at 11:28 AM, Skells, Mike <mike.skells@xxxxxxxx> wrote:

Hi,

Are these libraries included in your pom.xml?

Regards

Mike

 

From: m2e-users-bounces@xxxxxxxxxxx [mailto:m2e-users-bounces@xxxxxxxxxxx] On Behalf Of Tonny Madsen
Sent: 15 January 2013 10:19
To: m2e-users@xxxxxxxxxxx
Subject: [m2e-users] Update Project resets my .classpath if local libraries are included

 

I have a problem with a PDE project where Maven -> Update Project... seems to reset the .classpath of the project. Though this only seems to happen when the project includes a number of local jar files.

 

My original .classpath looks as follows:

 

<?xml version="1.0" encoding="UTF-8"?>

<classpath>

            <classpathentry exported="true" kind="lib" path="lib/commons-lang-2.2.jar"/>

            <classpathentry exported="true" kind="lib" path="lib/commons-configuration.jar"/>

            <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.6"/>

            <classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/>

            <classpathentry kind="src" path="src/"/>

            <classpathentry kind="output" path="target/classes"/>

</classpath>

 

And the reset version is reduced to:

 

<?xml version="1.0" encoding="UTF-8"?>

<classpath>

            <classpathentry kind="output" path="target/classes"/>

</classpath>

 

Which is a bit too limited :-) At the same time I get a dialog with the following error "lib/commons-configuration.jar [in ...] is not on the project's build path" (though I have no idea as which is the root cause)...

 

No other project exhibit the same problem. Removing the two libraries, "solves" the problem. The MANIFEST.MF and build.properties files are both correct and not changed in the process.

 

/Tonny

--

Tonny Madsen

My profiles:    

_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users

--

Tonny Madsen

My profiles:    

_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users