To the best of my knowledge, yes.
It appears Oracle Enterprise is slightly incompatible with m2e. I would suggest raising a bug, to have it properly investigated. Be prepared to create a minimal maven project showing the behavior.
Oh, and you do not have accidentially checked .project or .classpath or .settings into your sources? M2e works best if the maven projects do not have any Eclipse metadata in them when imported.
From: m2e-users-bounces@xxxxxxxxxxx [mailto:m2e-users-bounces@xxxxxxxxxxx] On Behalf Of Jarlath Reidy
Sent: 26. august 2013 15:38
To: Maven Integration for Eclipse users mailing list
Subject: Re: [m2e-users] Project configuration is not up-to-date with pom.xml
Hi Thorbjørn. Does that mean that if I use Maven from the command line I can ignore this?
I am running WebLogic server and have Oracle Enterprise for Eclipse installed from the marketplace.
On Mon, Aug 26, 2013 at 2:22 PM, Thorbjørn Ravn Andersen <thunderaxiom@xxxxxxxxxxx> wrote:
This is m2e that has become confused. This is irrelevant to command line maven runs.
Would “wls.ejb” be caused by your Eclipse having any weblogic tools installed or is there another cause?
I have errors with my Maven projects which I've just checked out from SVN (as Maven projects). I have the error:
"Project configuration is not up-to-date with pom.xml. Run Maven->Update Project or use Quick Fix."
But the quick fix doesn't actually work - it suggests running Maven->Update Project which yields another error:
An internal error occurred during: "Updating Maven Project". Version null of project facet wls.ejb does not exist.
Surprisingly, maven does build with "success". Can anyone enlighten me as to what the cause of this issue is and it's possible resolution?
m2e-users mailing list