Grails Publish Improvements

[jdaugherty]

There are 2 bugs I'm tracking down:

1. Sometimes when using the newer plugins {} method instead of apply plugin: 'org.grails.grails-publish' in a multiproject build it fails.
2. Having a simple build file at the root and including the plugin under a subproject can cause a failure (grails-spring-security-acl). For now the fix is to include the plugin at the root dependency and apply in the subproject.
   I'll create a ticket to look at these before the 7.0.0 release.

[jdaugherty]

These issues are not blockers and the plugin is still useful for most gradle publish scenarios. This ticket will be lower priority in the earlier Grails 7 development cycle.

[jdaugherty]

If root project = project, this can fail with:

• What went wrong:
  An exception occurred applying plugin request [id: 'org.grails.grails-publish']

Failed to apply plugin class 'io.github.gradlenexus.publishplugin.NexusPublishPlugin'.
Cannot run Project.afterEvaluate(Action) when the project is already evaluated.

[jdaugherty]

Releases are required to be signed when using grailsPublish. This ticket needs to add better documentation for these requirements.

[jdaugherty]

The grails-cache release had it's close SKIPPED: https://github.com/grails/grails-cache/actions/runs/13676792383/job/38239175486#step:6:60

This was because of a version not being properly committed. Since we know when a release/snapshot occurs, we should probably make a change like the one suggested here to ensure we configure that task correctly to prevent it's skipping.

[jdaugherty]

@matrei was able to figure out a way to have publishing and configure the publishing in a child project. Each child project would configure similar to the below:

      import org.grails.gradle.plugin.publishing.GrailsPublishExtension

      extensions.configure(GrailsPublishExtension) {
          // Explicit `it` is required here
          it.githubSlug = 'grails/grails-data-mapping'
          it.license.name = 'Apache-2.0'
          it.title = findProperty('pomTitle') ?: 'Grails GORM'
          it.desc = findProperty('pomDescription') ?: 'GORM - Grails Data Access Framework'
          it.developers = findProperty('pomDevelopers') as Map<String,String> ?: [
                  'graemerocher': 'Graeme Rocher',
                  'jeffscottbrown': 'Jeff Brown',
                  'burtbeckwith': 'Burt Beckwith',
                  'jameskleeh': 'James Kleeh',
                  'puneetbehl': 'Puneet Behl',
                  'jamesfredley': 'James Fredley'
          ]
      }

And then in the root build.gradle, it would be configured like so:

    // Workaround needed for nexus publishing bug
    // version and group must be specified in the root project
    // https://github.com/gradle-nexus/publish-plugin/issues/310
    version = projectVersion
    group = 'this.will.be.overridden'

    def publishedProjects = [
            'grails-datastore-async',
            'grails-datastore-core',
            'grails-datastore-gorm',
            'grails-datastore-gorm-async',
            //'grails-datastore-gorm-rx',
            'grails-datastore-gorm-support',
            'grails-datastore-gorm-tck',
            'grails-datastore-gorm-test',
            'grails-datastore-gorm-validation',
            'grails-datastore-web',
            'grails-gorm-testing-support',
    ]
    subprojects {
        if (name in publishedProjects) {
            // This has to be applied here
            apply plugin: 'org.grails.grails-publish'
        }
    }

Due to gradle-nexus/publish-plugin#81 I don't think it will be possible to fix the ignored multi project test cases, but this solution may be acceptable for most people to use composition based builds.

[jdaugherty]

I'm going to leave this open due to the aforementioned nexus publish bug, but we've mostly moved to evaluating the configuration at time of execution, which has meant that some scenarios with parent/child projects can now be supported. See the various grails-core projects for examples.