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

[Tonny Madsen <tonny.madsen@xxxxxxxxx>]

I have just noticed that I have the same problem if there are multiple src entries. This is often the case, when you use xtext, xcore, xtend or similar technologies in Eclipse. I have been using these technologies for a very long time and I have not noticed this problem before, so I really wonder how this should be a problem now.

/Tonny

On Tue, Jan 15, 2013 at 11:18 AM, Tonny Madsen <tonny.madsen@xxxxxxxxx> wrote:

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:    

--

Tonny Madsen

My profiles: