larry-cable commented on issue #321: URL: https://github.com/apache/maven-compiler-plugin/issues/321#issuecomment-2776920184
@desruisseaux downloaded 4.0.0-rc3, installed, cloned maven-compiler-plugin and pulled PR #320 built and installed in my local m2 repo and attempted to rebuild my patch module project... sadly the same results occur, compiler appears (my intuition) to no longer be resolving (java) dependencies against the pre-existing model that is the target of the --patch-module option... direct invocation of javac (24) with --patch-module compiles cleanly to further refine the failure mode, the packages that are not found during compilation are not exported from the target module... it appears to me as if somehow the behavior of the plugin w.r.t --patch-modules differs from that of javac; whereas javac when compiling the patch sources it will successfully satisfies references within the patch sources to pre-existing artifacts in the target module, whereas the plugin will not do so with any dependency that is not exported (public) from the (patch) target module itself. this renders the compiler plugin somewhat unusable for the purposes of compiling patch modules... and is not implementing the semantics of --patch-module in the same fashion as javac. -- 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
