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]

closeAndReleaseSonatypeStagingRepository is missing on subprojects when grailsPublish is applied there.