-
-
Notifications
You must be signed in to change notification settings - Fork 951
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 artifacts resolving as -plain #13743
Comments
@matrei can this logic be placed into |
Yes, I was thinking we should do that starting at 7.0.x. |
well, it's unwanted unexpected behavior that did not previously exist so probably should be corrected in 6.2.x and merged forward into 7.0.x |
Oh, ok, in which version did it start occurring? |
No matter, I'll add the change to grails-gradle-plugin 6.2.x instead 👍 |
@matrei I think it actually started with 6 |
Looks like it has been happening with hibernate5 plugin since 2021-05-29 13:37 and gsp starting with 5.0.0.RC1 (2021-07-20), but did NOT occur in < 5.0.0.M1 (2021-07-20) |
@matrei regarding your reverts, how do you want to handle
remove after revert? |
@codeconsole These can be removed again, as
Yes |
Closed by grails/grails-gradle-plugin#347 |
Tickets that will remove -plain from released versions grails/grails-gsp#546 - gsp & sitemesh2 |
Artifacts should not resolve as
-plain
unless a Spring boot version is also resolved. It is not proper convention to add -plain classifiers to artifacts.This could result in unwanted dependency resolution when gradle module files are also distributed.
The text was updated successfully, but these errors were encountered: