Community
Participate
Working Groups
Build Identifier: Bugs #355292 and #349986 affecting mavenarchiver and m2e-wtp plugins are caused by plugin configurations using project.parent.* properties. As a matter of fact, calling mavenProject.getParent() in AbstractBuildParticipant.build() causes this exception : java.lang.IllegalStateException: no context maven session at org.eclipse.m2e.core.internal.embedder.ContextRepositorySystemSessionImpl.getSession(ContextRepositorySystemSessionImpl.java:48) at org.eclipse.m2e.core.internal.embedder.ContextRepositorySystemSessionImpl.getMirrorSelector(ContextRepositorySystemSessionImpl.java:102) at org.sonatype.aether.impl.internal.DefaultRemoteRepositoryManager.aggregateRepositories(DefaultRemoteRepositoryManager.java:139) at org.apache.maven.project.ProjectModelResolver.addRepository(ProjectModelResolver.java:119) at org.apache.maven.model.building.DefaultModelBuilder.configureResolver(DefaultModelBuilder.java:567) at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:306) at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:232) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:135) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:98) at org.apache.maven.project.MavenProject.getParent(MavenProject.java:359) As a workaround, the parent projects can be manually loaded in each BuildParticipant implementations, but a proper solution would be to attach (and later detach) each project being built to the current maven session. The same goes for projects being configured by project configurators. Reproducible: Always
@fred can you check if latest 1.4 is still affected? This issue may have been addressed as a side effect of introduction of IMavenExecutionContext.
Closing old/stale bugreport
Moved to https://github.com/eclipse-m2e/m2e-core/issues/