Hello all
The proposed maven-compiler-plugin version 4 now passes the integration
tests. It has reached a state where it could (theoretically) be used
instead of version 3, but there is probably some more bugs to discover.
Many tests had to be modified, and a few of them have been deleted. The
modifications and deletions are documented in a wiki page at [1]. More
information about incompatible changes (the reasons why some tests have
been modified or deleted) are documented at [2].
The work is a single monster commit [3] because the intermediate steps
didn't built. The work had to be done fully for being buildable and
testable. It requires two pull requests on Maven core: [4] and [5]. The
first one is a bug fix. The second one introduces a new API and may need
discussion. I will send separated emails for discussion points.
The work is far from finished. Now we have a possible substitute for
version 3 of the plugin, but the next work (in addition to extensive
testing, bug fixes and improvements) will be addition of proposed new
features for better multi-releases and Java modules support. One new
feature already there is that the new plugin obeys to the new
"modular-jar" and "classpath-jar" dependency types for forcing the
placement of a dependency on the module-path or on the class-path.
Martin
[1]https://github.com/Geomatys/maven-compiler-plugin/wiki/Test-changes
[2]https://github.com/Geomatys/maven-compiler-plugin/wiki/Incompatible-changes
[3]https://github.com/Geomatys/maven-compiler-plugin/commits/master/
[4]https://github.com/apache/maven/pull/1621
[5]https://github.com/apache/maven/pull/1625
