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)