grails-plugins/grails-release — pull request #7 by selera (2012-05-06 08:42:04+00:00)
Title: Ignore pom.xml during generatePom if grails.project.dependency.resolution contains "pom(false)"

This allows the selera grails-wrapper-plugin to use the release plugin.

With the wrapper approach, a very trivial pom.xml is used to drive the build lifecycle, but the grails module dependencies are still managed entirely within grails via BuildConfig.groovy, like a 'normal' grails project.

So when we are installing a binary plugin into the local m2 repo via "maven-install", we want the release plugin to ignore this trivial driver pom (which doesn't have any dependency information) and generate a pom the same way it would if the pom didn't exist.

Using "pom false" inside BuildConfig.groovy looks like a clean and meaningful way to convey this to the grails subsystem. No mean side effects. No impact to grails users who don't use the wrapper plugin - aka 99.99% of grails users :-)