Skip to content
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

Use versions from grails-bom in additional locations #510

Merged
merged 3 commits into from
Feb 14, 2025

Conversation

jamesfredley
Copy link
Contributor

  • Use versions from grails-bom in additional locations
  • add grail-bom to buildscript{} to pull in versions
  • put assetPipelineGradleVersion in gradle.properties
  • update dependency versions not provided by grails-bom

add grail-bom to buildscript{} to pull in versions
put assetPipelineGradleVersion in gradle.properties
update dependency versions not provided by grails-bom
@jamesfredley jamesfredley added this to the grails:7.0.0-M2 milestone Feb 13, 2025
@@ -60,6 +60,13 @@ public void apply(GeneratorContext generatorContext) {
.version("$grailsVersion")
.implementation());

generatorContext.addBuildscriptDependency(Dependency.builder()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you're including the bom, you don't need an asset pipeline version. It's in the bom.

Copy link
Contributor Author

@jamesfredley jamesfredley Feb 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For asset-pipeline we are using id to load the plugin from the Gradle plugin portal and I have not found a way to reference the grails-bom version for use with id in the plugins{} block.

Copy link
Contributor

@jdaugherty jdaugherty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm assuming the intent of this change is to use the bom for the gradle buildscript as well? If so, the asset pipeline version is not needed.

Copy link
Contributor

@matrei matrei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a step forward. James D has valid points. But lets do it incrementally if it is not an easy solve, there are many moving parts here.

@jamesfredley jamesfredley self-assigned this Feb 13, 2025
@jamesfredley jamesfredley merged commit d617279 into 7.0.x Feb 14, 2025
9 checks passed
@jamesfredley jamesfredley deleted the more-version-updates branch February 14, 2025 21:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants