`Cannot access Key[MavenProject, annotation=[none]] outside of a scoping block` with m-jar-p 3.5.0

[pzygielo]

After updating maven-jar-plugin from 3.4.2 to 3.5.0 the Problems view started to show:

Cannot access Key[type=org.apache.maven.project.MavenProject, annotation=[none]] outside of a scoping block	pom.xml	/...

IDE: Version: 2025-09 (4.37.0), Build id: 20250905-1456
M2E - Maven Integration for Eclipse 2.9.1.20250811-2022
M2E - POM Editor using LemMinX language server (includes Incubating components) 2.6.101.20250727-0612
JDK: temurin 25

If I downgrade m-jar-p back to 3.4.2 and do Maven -> Update Project - then the (error) Problems are gone, which suggests to me - there is something interesting with that new plugin.

[laeubi]

Can you check if there is a stracktrace for the error?

[pzygielo]

From Error-Log view - I see 2 categories of warnings, of which the first mentions OutOfScopeException:

1. Error injecting: org.apache.maven.plugins.jar.JarMojo

com.google.inject.ProvisionException_: Unable to provision, see the following errors:
1) [Guice/ErrorInCustomProvider]: OutOfScopeException: Cannot access Key[type=MavenProject, annotation=[none]] outside of a scoping block
  at MojoExecutionScopeModule.configure(MojoExecutionScopeModule.java:47)
      \_ installed by: WireModule -> MojoExecutionScopeModule
  at JarMojo.<init>(JarMojo.java:72)
      \_ for 1st parameter
  while locating JarMojo

Learn more:
  https://github.com/google/guice/wiki/ERROR_IN_CUSTOM_PROVIDER

1 error

======================
Full classname legend:
======================
JarMojo:                  "org.apache.maven.plugins.jar.JarMojo"
MavenProject:             "org.apache.maven.project.MavenProject"
MojoExecutionScopeModule: "org.apache.maven.execution.scope.internal.MojoExecutionScopeModule"
OutOfScopeException:      "com.google.inject.OutOfScopeException"
WireModule:               "org.eclipse.sisu.wire.WireModule"
========================
End of classname legend:
========================

	at com.google.inject.internal.InternalProvisionException.toProvisionException(InternalProvisionException.java:251)
	at com.google.inject.internal.InjectorImpl$1.get(InjectorImpl.java:1104)
	at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1139)
	at org.eclipse.sisu.space.AbstractDeferredClass.get(AbstractDeferredClass.java:50)
	at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:86)
	at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:57)
	at com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFactory.java:67)
	at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:109)
	at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:124)
	at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:66)
	at com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:62)
	at com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:47)
	at com.google.inject.internal.InjectorImpl$1.get(InjectorImpl.java:1101)
	at org.eclipse.sisu.inject.Guice4$2.get(Guice4.java:235)
	at org.eclipse.sisu.inject.LazyBeanEntry.getValue(LazyBeanEntry.java:83)
	at org.eclipse.sisu.plexus.LazyPlexusBean.getValue(LazyPlexusBean.java:53)
	at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:267)
	at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:259)
	at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:491)
	at org.eclipse.m2e.core.internal.embedder.MavenImpl.getConfiguredMojo(MavenImpl.java:206)
	at org.eclipse.m2e.mavenarchiver.internal.AbstractMavenArchiverConfigurator.reflectManifestGeneration(AbstractMavenArchiverConfigurator.java:439)
	at org.eclipse.m2e.mavenarchiver.internal.AbstractMavenArchiverConfigurator.lambda$3(AbstractMavenArchiverConfigurator.java:398)
	at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:458)
	at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:339)
	at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:278)
	at org.eclipse.m2e.mavenarchiver.internal.AbstractMavenArchiverConfigurator.generateManifest(AbstractMavenArchiverConfigurator.java:371)
	at org.eclipse.m2e.mavenarchiver.internal.AbstractMavenArchiverConfigurator.mavenProjectChanged(AbstractMavenArchiverConfigurator.java:228)
	at org.eclipse.m2e.mavenarchiver.internal.AbstractMavenArchiverConfigurator$1.build(AbstractMavenArchiverConfigurator.java:178)
	at org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.lambda$2(MavenBuilderImpl.java:159)
	at java.base/java.util.LinkedHashMap.forEach(LinkedHashMap.java:986)
	at org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:139)
	at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:164)
	at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:1)
	at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.lambda$1(MavenBuilder.java:109)
	at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:458)
	at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:292)
	at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.lambda$0(MavenBuilder.java:100)
	at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:458)
	at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:339)
	at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:278)
	at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:83)
	at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:192)
	at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:1109)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:47)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:299)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:355)
	at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:449)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:47)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:452)
	at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:564)
	at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:512)
	at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:594)
	at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:208)
	at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:309)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Caused by: com.google.inject.OutOfScopeException: Cannot access Key[type=org.apache.maven.project.MavenProject, annotation=[none]] outside of a scoping block
	at org.apache.maven.execution.scope.internal.MojoExecutionScope$2.get(MojoExecutionScope.java:99)
	at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:45)
	at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:40)
	at com.google.inject.internal.SingleParameterInjector.getAll(SingleParameterInjector.java:60)
	at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:113)
	at com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:33)
	at com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:98)
	at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:109)
	at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:124)
	at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:66)
	at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:93)
	at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:300)
	at com.google.inject.internal.InjectorImpl$1.get(InjectorImpl.java:1101)
	... 53 more

2. Direct modification of compileSourceRoots through clear() is deprecated and will not work in Maven 4.0.0. Please use the add/remove methods instead. If you're using a plugin that causes this warning, please upgrade to the latest version and report an issue if the warning persists. To disable these warnings, set -Dmaven.project.sourceRoots.warningsDisabled=true on the command line, in the .mvn/maven.config file, or in project POM properties.

An exception stack trace is not available.

[pzygielo]

• Migrate component injection to JSR-330 apache/maven-jar-plugin#492

Also bisected m-jar-p to the commit introduced with above PR:

ef8ed4cf89bcacb2f8ad5c3f4492ba186ead4409 is the first bad commit

[kwin]

This seems to be related to injecting MavenProject.

The SessionScope is seeded in

m2e-core/org.eclipse.m2e.core/src/org/eclipse/m2e/core/internal/embedder/MavenExecutionContext.java

Line 339 in 2bac0fc

sessionScope.seed(MavenSession.class, session);

, however the underlying MavenSession does not seem to have a current project being set in

m2e-core/org.eclipse.m2e.core/src/org/eclipse/m2e/core/internal/embedder/MavenExecutionContext.java

Line 325 in 2bac0fc

setValue(CTX_MAVENSESSION,

.

In Maven 4 CLI the MavenExecutionScope is seeded from the MavenSession https://github.com/apache/maven/blob/44af8f13be37016e2c6a400ed73aba618c30a792/impl/maven-core/src/main/java/org/apache/maven/plugin/DefaultBuildPluginManager.java#L123 while in Maven 3.x this is seeded in https://github.com/apache/maven/blob/8c3803526036cdfdacd6479da80993cc9821461a/maven-core/src/main/java/org/apache/maven/plugin/DefaultBuildPluginManager.java#L121.

The error message Cannot access Key ... outside of a scoping block is emitted by https://github.com/apache/maven/blob/8c3803526036cdfdacd6479da80993cc9821461a/maven-core/src/main/java/org/apache/maven/execution/scope/internal/MojoExecutionScope.java#L122.

The stack trace implies this is triggered from

m2e-core/org.eclipse.m2e.mavenarchiver/src/org/eclipse/m2e/mavenarchiver/internal/AbstractMavenArchiverConfigurator.java

Line 228 in 2bac0fc

generateManifest(newFacade, manifest, monitor);

(i.e. outside the regular execution of the mojo).

[in-fke]

First of all, upon refreshing, I see the same type of errors twice.

Then, it's probably the same errors as above

com.google.inject.ProvisionException: Unable to provision, see the following errors:

1) [Guice/ErrorInCustomProvider]: OutOfScopeException: Cannot access Key[type=MavenProject, annotation=[none]] outside of a scoping block
  at MojoExecutionScopeModule.configure(MojoExecutionScopeModule.java:47)
      \_ installed by: WireModule -> MojoExecutionScopeModule
  at JarMojo.<init>(JarMojo.java:72)
      \_ for 1st parameter
  while locating JarMojo

Learn more:
  https://github.com/google/guice/wiki/ERROR_IN_CUSTOM_PROVIDER

1 error

======================
Full classname legend:
======================
JarMojo:                  "org.apache.maven.plugins.jar.JarMojo"
MavenProject:             "org.apache.maven.project.MavenProject"
MojoExecutionScopeModule: "org.apache.maven.execution.scope.internal.MojoExecutionScopeModule"
OutOfScopeException:      "com.google.inject.OutOfScopeException"
WireModule:               "org.eclipse.sisu.wire.WireModule"
========================
End of classname legend:
========================

Using maven-jar-plugin 3.5.0 and Maven External 3.9.7

[kwin]

This is a general issue with org.eclipse.m2e.core.internal.embedder.MavenImpl.getConfiguredMojo() whenever the Mojo relies on JSR 330 annotations. That always fails when the used scope (MojoExecutionScope) is accessed without being "entered". It can be seen in https://github.com/apache/maven/blob/8c3803526036cdfdacd6479da80993cc9821461a/maven-core/src/main/java/org/apache/maven/plugin/DefaultBuildPluginManager.java#L117 how this done by Maven internally when executing the mojo.