-
Notifications
You must be signed in to change notification settings - Fork 46
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
🐛 Fix compile step #397
🐛 Fix compile step #397
Conversation
CAUTION: This works currently only with a newer version of Maven (tested with 3.9.5). Signed-off-by: Gerd Aschemann <gerd@aschemann.net>
…Maven process Signed-off-by: Gerd Aschemann <gerd@aschemann.net>
Signed-off-by: Juan Manuel Leflet Estrada <jleflete@redhat.com>
Do we have a multi-module test case yet? I would love to see that added with/ this change to make sure we don't break that in the future (I am worried about me breaking it :) ) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this completely fix #392?
Captured in issue here, will add sometime this week #399 |
If it helps: The problem came up in my (company project) multi module build. Tested the patch with that project already. |
Thanks! |
Fixes #393
Remove "compile" goal from maven invocations, as some applications may not be compilable with the JDK version we bundle.
Related to #393 and #393