gnodet commented on PR #1401: URL: https://github.com/apache/maven/pull/1401#issuecomment-1973493856
> Fine for me. I added [one more commit](https://github.com/Geomatys/maven/commit/75d8e88046e38cb30134c34eb731c226f4dfce87) for allowing plugins to log warning to users when a dependency cannot be placed on any path. > > After the merge, I would like to try the new API in `maven-compiler-plugin` and create a new merge request for it. Sounds good. You'll need to build the following branches: * https://github.com/apache/maven-plugin-tools/pull/242 * https://github.com/apache/maven-plugin-testing/pull/39 * https://github.com/apache/maven-compiler-plugin/pull/147 The above maven-compiler-plugin PR can be used as a basis, as it is already has all the migration to the v4 api. If the underlying plexus-compiler API does not support the needed features to fully leverage the new jpms support, a possibility would be to change the m-compiler-p to simply wrap the `javac` compiler instead of trying to abstract all implementations. The other one is the eclipse compiler, not sure they are really others. If needed, we'd end up with two plugins, but they may ease the mapping of various options... We discussed that with @cstamas ... -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
