"Project configuration is not up-to-date with pom.xml"

[luismcv]

I'm having the same issue described here:

ENTRY org.eclipse.core.resources 2 568 2013-02-26 20:07:21.170
!MESSAGE Problems encountered while setting project description.
!SUBENTRY 1 org.eclipse.core.resources 2 35 2013-02-26 20:07:21.170
!MESSAGE Cannot remove nature org.springframework.ide.eclipse.core.springnature because it is a prerequisite of nature com.springsource.sts.roo.core.nature.

Using Spring IDE 3.1.0.201210040510-RELEASE under Indigo Service Release 2

I have tried many things, even removing the project from eclipse, run eclipse:clean, import the project again as an existing maven project.

My .project file contents are:

<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
<name>xxxxxxx-model</name>
<comment></comment>
<projects>
</projects>
<buildSpec>
<buildCommand>
<name>org.eclipse.ajdt.core.ajbuilder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>org.springframework.ide.eclipse.core.springb uilder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>org.eclipse.m2e.core.maven2Builder</name>
<arguments>
</arguments>
</buildCommand>
</buildSpec>
<natures>
<nature>com.springsource.sts.roo.core.nature</nature>
<nature>org.springframework.ide.eclipse.core.sprin gnature</nature>
<nature>org.eclipse.ajdt.ui.ajnature</nature>
<nature>org.eclipse.jdt.core.javanature</nature>
<nature>org.eclipse.m2e.core.maven2Nature</nature>
</natures>
</projectDescription>

Any guidance would be really appreciated. Thanks.

[Andrew Eisenberg]

Not too sure what is happening. Any chance you can share the project?

[luismcv]

Out of desperation I started to simplify the pom.xml and I've found that it's related to using expressions in the parent.version tag. If I replace them with some constant version number, Maven->Project Update... doesn't fail anymore.

But it's estrange, because I use expressions in other sub-projects too without causing any problems. The only difference somewhat related to the error message is that this project does indeed use ROO. And no, the springnature doesn't get removed from those sub-projects after doing a Project Update. Shame the plugin doesn't give more detailed logs.

Anyway, maven also gives warnings against using expressions, so I guess it's time to find another way of doing what I was doing with them.

[Andrew Eisenberg]

Thanks for the reply. It does sound like this is a limitation of the m2e plugin.

[nabil.oufkkir]

I seem to fall into an odd loop in some of my simple Roo projects.

At some point I get the Marker under "Maven problems" with the message "Project configuration is not up-to-date with pom.xml. Run project configuration update".
I do what is asked and run Maven -> "update project configuration" from the right-click popup menu and I choose to update dependencies for the codebase of the project. When I do I'm noticed "Unable to update maven configuration" with error "problems encountered when setting project description".
Sometimes I also get the submessage that "Cannot remove nature org.springframework.ide.eclipse.core.springnature because it is a prerequisite of nature com.springsource.sts.roo.core.nature."

I tried a couple of times to remove and re-add the natures in question, which resolved the problem temporarily. Any small change to the pom starts this cycle once more however.

Project was created with Roo and some changes made to the pom. The project in use validates, compiles and tests run green.

STS 2.8.1.RELEASE fresh install with Mercurial, Infinitest. For maven (external 3.03) I added the plugins maven-builder-helper, Failsafe and Cargo.

I need to get out of this cycle now. Any ideas or thoughts?

1 - Open Marker View
2 - Right-click on the Error message
3 - Select Quick Fix
4 - Click Finish

[luismcv]

It turned out my problem wasn't related to expressions in the parent.version tag, as the error came back later. I guess that something else that I did, "fixed" the issue temporary.

I later realised that my parent project also had the org.springframework.ide.eclipse.core.springnature and com.springsource.sts.roo.core.nature natures, that were left there and not used anymore since the project was split in modules. So I removed them, and I haven't seen the error since.

[Martin Lippert]

Hey!

Glad to hear its working now and thanks for the additional details!!!

Cheers,
Martin