|Re: [m2e-users] Project configuration is not up-to-date with pom.xml|
Don't report this as an m2e bug unless the problem can be reproduced
On 2013-08-27 3:32 AM, Thorbjørn Ravn Andersen wrote:
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.
without Oracle Enterprise.This is not true. m2e is expected to work with eclipse metadata files
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.
shared via version control system. m2e considers these files as derived
from pom.xml and will overwrite them as necessary.
[mailto:firstname.lastname@example.org] *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
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 <mailto:email@example.com>> wrote:*From:*firstname.lastname@example.org
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?
<mailto:email@example.com>] *On Behalf Of *Jarlath Reidy
*Sent:* 26. august 2013 13:42
*To:* m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>
*Subject:* [m2e-users] Project configuration is not up-to-date with pom.xmlm2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>
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?
Thanks & regards,
m2e-users mailing list
Back to the top