[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [m2e-users] Project configuration is not up-to-date with pom.xml
- From: "Richard Sand" <rsand@xxxxxxxxxxxxxx>
- Date: Tue, 27 Aug 2013 08:41:17 -0400
- Delivered-to: email@example.com
- Thread-index: AQK+6quF9Xm34DpL/xb0f7VUZjmldQJdOSXwAcIpYJ4B3fq8JwKw511Rl4L8XPA=
+1 Igor on both points.
It sounds to me like wls.ejb is a facet specifically for WLS. It would be
Oracle's responsibility to make sure their stuff works with m2e.
Regarding classpaths, years ago I would always exclude .classpath, .project,
and my eclipse settings as svn:ignore, but I've done a 180 on this stance,
because the tools are adept at handling it. Particularly with the release of
m2e, the project and classpath settings remain consistent across multiple
development environments. I've been very happy with how m2e has handled
From: m2e-users-bounces@xxxxxxxxxxx [mailto:m2e-users-bounces@xxxxxxxxxxx]
On Behalf Of Igor Fedorenko
Sent: Tuesday, August 27, 2013 8:17 AM
Subject: Re: [m2e-users] Project configuration is not up-to-date with
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.
Don't report this as an m2e bug unless the problem can be reproduced without
> 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.
This is not true. m2e is expected to work with eclipse metadata files shared
via version control system. m2e considers these files as derived from
pom.xml and will overwrite them as necessary.
> [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 <mailto: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?
> <mailto:m2e-users-bounces@xxxxxxxxxxx>] *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
> 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
> m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>
> m2e-users mailing list
m2e-users mailing list