GuntherRademacher opened a new issue, #507: URL: https://github.com/apache/maven-jar-plugin/issues/507
### Affected version 3.5.0 ### Bug description After [upgrading](https://github.com/BaseXdb/basex/commit/42f793899abe135e953c78e26b3b3ba3e0d14c5a) maven-jar-plugin from 3.4.2 to 3.5.0, Eclipse m2e begins reporting the following Maven configuration error on the project's pom.xml: ```txt Cannot access Key[type=org.apache.maven.project.MavenProject, annotation=[none]] outside of a scoping block ``` This error appears only inside Eclipse (m2e). The project builds successfully with Maven CLI (mvn clean package). [Downgrading](https://github.com/BaseXdb/basex/commit/1b7a67316c8cf181087becf80a074e437ef2038a) back to 3.4.2 consistently removes the error. This strongly suggests that a change in 3.5.0 triggers a Guice/Sisu scope violation during mojo configuration - something m2e does differently from CLI builds. **Environment** - Eclipse IDE: 2025-09 release - m2e: default version bundled with Eclipse 2025-09 - Embedded Maven in Eclipse: 3.9.11 - External Maven via CLI: 3.9.x (works fine) - Java version: 17 - OS: Windows 11 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
