This issue has raised it's head again. I would be happy with a workaround
for this. When I run Maven -> Update Project, if I uncheck "Update project
configuration from pom.xml" then I don't get this error. However then I am
left with the original problem where eclipse complains that "Project
configuration is not up-to-date with pom.xml" under Markers->Maven Problems.
If Igor represents the thinking of the m2e developers then I imagine there
is no point in reporting this. I'd be happy with a workaround.
*Session Data:*
eclipse.buildId=4.3.0.M20130911-1000
java.version=1.7.0_40
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_IE
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -data C:\Users\reidyja\workspace\SA1402 -os win32
-ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product
And here is the *stack trace:*
java.lang.IllegalArgumentException: Version null of project facet wls.ejb
does not exist.
at
org.eclipse.wst.common.project.facet.core.util.internal.Versionable.getVersion(Versionable.java:80)
at
org.eclipse.wst.common.project.facet.core.internal.ProjectFacet.getVersion(ProjectFacet.java:1)
at
oracle.eclipse.tools.maven.adf.project.configurator.ADFEJBProjectConfigurator.getRequiredFacetVersions(ADFEJBProjectConfigurator.java:31)
at
oracle.eclipse.tools.maven.adf.project.configurator.AbstractADFProjectConfigurator.configure(AbstractADFProjectConfigurator.java:85)
at
org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:109)
at
org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:472)
at
org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:161)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:137)
at
org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:465)
at
org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration0(ProjectConfigurationManager.java:403)
at
org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:316)
at
org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:1)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:161)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:137)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:89)
at
org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1301)
at
org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:313)
at
org.eclipse.m2e.core.ui.internal.UpdateMavenProjectJob.runInWorkspace(UpdateMavenProjectJob.java:77)
at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
On Wed, Aug 28, 2013 at 9:13 AM, Ilko Iliev <ilkomil...@gmail.com> wrote:
> regarding metadata - m2e handles them correctly, however the scm has
> troubles with them, because they are in conflict, if say the developer 1
> references them via maven repo and developer 2 has them in the local
> workbench (maintainer of the lib)... so, we removed them at last from our
> subversion repository. I don't have experience with other scm tools
>
>
>
> On Tue, Aug 27, 2013 at 2:16 PM, Igor Fedorenko <i...@ifedorenko.com>wrote:
>
>>
>>
>> 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 Oracle Enterprise.
>>
>>
>>
>>> 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.
>>
>> --
>> Regards,
>> Igor
>>
>>
>>
>>> *From:*m2e-users-boun...@eclipse.org
>>> [mailto:m2e-users-boun...@eclipse.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
>>>
>>> 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
>>> <thunderax...@hotmail.com <mailto:thunderax...@hotmail.com>> 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?
>>>
>>> *From:*m2e-users-boun...@eclipse.org
>>> <mailto:m2e-users-boun...@eclipse.org>
>>> [mailto:m2e-users-boun...@eclipse.org
>>> <mailto:m2e-users-boun...@eclipse.org>] *On Behalf Of *Jarlath Reidy
>>> *Sent:* 26. august 2013 13:42
>>> *To:* m2e-users@eclipse.org <mailto:m2e-users@eclipse.org>
>>> *Subject:* [m2e-users] Project configuration is not up-to-date with
>>> pom.xml
>>>
>>>
>>> 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,
>>>
>>> Jarlath
>>>
>>>
>>> _______________________________________________
>>> m2e-users mailing list
>>> m2e-users@eclipse.org <mailto:m2e-users@eclipse.org>
>>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> m2e-users mailing list
>>> m2e-users@eclipse.org
>>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>>>
>>> _______________________________________________
>> m2e-users mailing list
>> m2e-users@eclipse.org
>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>>
>
>
> _______________________________________________
> m2e-users mailing list
> m2e-users@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/m2e-users
>
>
_______________________________________________
m2e-users mailing list
m2e-users@eclipse.org
https://dev.eclipse.org/mailman/listinfo/m2e-users
