Hello all
The proposed new compiler plugin has been updated with the following
changes:
* Use of ASM for rewriting the module-info.java file on JDK older than
22 has been reintroduced (for reproductible builds).
* Support for overwriting module-info.java in the tests has been
reimplemented, but in a way quite different than Maven 3. See [1].
The attempt to be clever regarding --source versus --release options has
not been reintroduced yet, but would be easy to do if it appears
desirable. Before to do so, I would be curious to see if collisions
between those two options happen often, and if so, if they appear in
places that we can adjust (e.g. in an inherited POM). If it appears that
Maven 3 behavior should be kept, maybe it would be worth to start a
discussion about whether to introduce a "compatibility mode"?
We have one test failure, but I'm not sure that it come from the
compiler. It seems to come from Maven core. If anyone has some clue
about [2], it would be appreciated.
Martin
[1]https://github.com/Geomatys/maven-compiler-plugin/wiki/Implementation-changes#overwriting-module-info-in-tests
[2]https://github.com/apache/maven-compiler-plugin/pull/269#issuecomment-2441456531
