-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BinaryModuleInfoParser.parse does not take toolchain into account #64
Comments
I checked out the latest snapshot 3.9.0 of the compiler plugin, installed locally and used that in my real life repo together with plexus-java 1.0.6 and I got a warning and a compilation error:
So I managed to set up a test multi module repo with a parent and 2 children where child2 depends on child1 https://github.com/torakiki/test and I get the same result, using maven compiler 3.9.0-SNAPSHOT and plexus-java 1.0.6:
From what I can see from the logs child1 module is actually missing from the module path. |
Yes, both the test repo and my actual repo are compiling fine |
Fixed with 249f8bd |
When scanning existing files,
org.codehaus.plexus.languages.java.jpms.LocationManager.resolvePaths
will take a scanning request containing a possible JavaHome location.But the BinaryModuleInfoParser does not use this javaHome location,, resulting in:
Downstream issue and how to reproduce in a single, repeated step (try
mvn compile
twice):https://issues.apache.org/jira/browse/MCOMPILER-455
The text was updated successfully, but these errors were encountered: