-
Notifications
You must be signed in to change notification settings - Fork 21
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
Toolchain awereness #29
Comments
what "switching the jvm" do you mean? gmaven 2 uses the existing JVM to execute Groovy implementations, not sure how becoming toolchain aware helps, but maybe i'm missing something? |
I support this issue. It's a real problem the plugin not supporting toolchains. |
FTR I still do not really get what the value of "toolchains" are here, but if someone can explain it to me or provide a PR to express the value i'm certainly open to considering supporting it. |
Here's my scenario: I'm working on a large project that's composed of various modules. While each module depends on the parent's properties, it also has its own dependencies and requires specific JDK settings for source and target versions. To build the parent project with all its modules, I'm using toolchains that support multiple JDK versions (1.8, 11, 13, and 17). Most of the plugins I'm using also support toolchains. However, I've encountered an issue with gmaven, which is used by one of the new modules I'm working on. |
Make groovy-maven-plugin aware of settings maven-toolchains-plugin. In speciall switching the jvm.
The text was updated successfully, but these errors were encountered: