fix artifacts resolving as -plain

[codeconsole]

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.

   136374  10-11-2024 20:07   BOOT-INF/lib/asset-pipeline-grails-4.5.1-plain.jar
   330271  10-10-2024 05:31   BOOT-INF/lib/gsp-6.2.2-plain.jar
    46996  10-10-2024 05:31   BOOT-INF/lib/sitemesh2-6.2.2-plain.jar
    58173  10-11-2024 20:07   BOOT-INF/lib/hibernate5-8.1.0-plain.jar
   144196  10-10-2024 05:33   BOOT-INF/lib/fields-5.1.0-plain.jar

[matrei]

grails/grails-gsp#525

[matrei]

grails/fields#377

[matrei]

grails/grails-data-hibernate5#917

[codeconsole]

@matrei can this logic be placed into grails-gradle-plugin instead so that it always is applied to plugins?

[matrei]

Yes, I was thinking we should do that starting at 7.0.x.

[codeconsole]

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

[matrei]

Oh, ok, in which version did it start occurring?

[matrei]

No matter, I'll add the change to grails-gradle-plugin 6.2.x instead 👍

[codeconsole]

@matrei I think it actually started with 6

[codeconsole]

Looks like it has been happening with hibernate5 plugin since 2021-05-29 13:37
https://repo.maven.apache.org/maven2/org/grails/plugins/hibernate5/

and gsp starting with 5.0.0.RC1 (2021-07-20), but did NOT occur in < 5.0.0.M1 (2021-07-20)
https://repo.maven.apache.org/maven2/org/grails/plugins/gsp/