-
Notifications
You must be signed in to change notification settings - Fork 35
Bump org.gradlex:gradle-module-metadata-maven-plugin to 1.2 #106
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
Bump org.gradlex:gradle-module-metadata-maven-plugin to 1.2 #106
Conversation
Would it make sense to merge this against |
@cowtowncoder yes. This won't break anything. Feel free to change as you see fit. Or I can redo the branch against 2.18 tomorrow. |
cbf7b8d
to
b5fc59e
Compare
b5fc59e
to
dc8a935
Compare
PR targets EDIT: Just realized that this would include the |
@jjohannes Oh. Good point. This increases risk by quite a bit -- so, let's actually target 2.x (for 2.20). Apologies for missing this & making you re-do changes. We also need similar changes against |
With this users won't run into the following specific Gradle issue with future Jackson releases: gradlex-org/gradle-module-metadata-maven-plugin#45 Signed-off-by: Jendrik Johannes <[email protected]>
dc8a935
to
eb0e0e0
Compare
Retargeted to |
Just realized this is safe for 2.19 too, will backport after merging. |
Backport #106 from 2.20 to 2.19(.2)
Merged, backported in 2.19 for 2.19.2. |
With this users won't run into the following specific Gradle issue with future Jackson releases:
gradlex-org/gradle-module-metadata-maven-plugin#45