slachiewicz commented on issue #14015:
URL: https://github.com/apache/maven/issues/14015#issuecomment-6900076558

   Wider impact: this is not specific to groovy-eclipse-compiler. Any build 
extension (`<extensions>true</extensions>`) or core extension 
(`.mvn/extensions.xml`) that registers a `LifecycleMapping` for a packaging 
core already maps (`jar`, `war`, `ejb`, `rar`, `pom`, `maven-plugin`, …) is 
ignored on 3.10.1 and 3.10.2-SNAPSHOT. The build stays green: the extension's 
goals do not run, tests are not run, the artifact has no classes, and core's 
default plugin versions replace the ones the extension pins.
   
   Tested on 3.10.1 against 3.10.0 and 3.10.1 with #14016:
   
   | Setup | 3.10.1 | 3.10.0 / with #14016 |
   |---|---|---|
   | kotlin-maven-plugin 2.2.21 with `<extensions>true</extensions>`, as the 
[Kotlin Maven docs](https://kotlinlang.org/docs/maven-configure-project.html) 
prescribe (overrides `jar`, `ejb`, `war`, `rar`) | no `kotlin:*` goal runs, jar 
without classes, BUILD SUCCESS | `kapt`, `compile`, `test-kapt`, `test-compile` 
run |
   | kotlin-maven-plugin 2.2.21 as a core extension in `.mvn/extensions.xml` | 
same as above | same as above |
   | groovy-eclipse-compiler 3.9.1 (overrides `jar`, `war`, `rar`, `ejb`, 
`maven-plugin`) | `add-groovy-build-paths` missing, no classes, no tests | 
works |
   | Multi-module, extension in one module | that module's jar is empty, the 
others are fine, BUILD SUCCESS | works |
   
   Other published plugins that override a core packaging and are likely 
affected, not built: takari-lifecycle-plugin (`pom`, binds its own 
install/deploy), micronaut-maven-plugin (`jar`, enabled as an extension by 
micronaut-parent), sarl-maven-plugin (`jar`), artifactory-maven-plugin (`jar`), 
node-maven-plugin (`war`).
   
   Not affected: extensions that only add a new packaging, such as Tycho, Felix 
`bundle`, `nar`, `nbm` and Karaf `kar`, since a single entry survives the copy. 
3.9.16, 3.9.17-SNAPSHOT, 4.0.0-rc-7, 4.0.0-SNAPSHOT and 4.2.0-SNAPSHOT are not 
affected.
   
   Workarounds on 3.10.1: bind the extension's goals with explicit executions 
in the POM (verified for groovy-eclipse-compiler), or use 3.10.0 or 3.9.x. 
Pinning plugin versions does not help. Artifacts built with 3.10.1 by affected 
projects should be checked before release.
   


-- 
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]

Reply via email to