The build dependency on spring-webflow should not be exported; if it is, it can conflict/override a dependency on a differing version of spring-webflow in the application that is using page-resources. In my case, this resulted in the inability to start my application.
Hrm, so I think this change ended up being a bad one. If I now depend on page-resources 0.2.2 in a "vanilla" Grails project, the page-resources plugin fails to build when I issue a 'run-app' command. If I depend on version 0.2.1, it builds successfully.
It seems that testing a plugin by doing a local 'package-plugin' and then 'install-plugin' is not equivalent to using the plugin when it is retrieved from the Grails plugins repo. For some reason the dependencies related to the plugin seem to behave differently between the two.
At the moment, it seems like my change should be reverted. A workaround for projects that directly depend on spring-webflow and aren't compatible with the version depended on by page-resources is to exclude the page-resources dependency in the project's BuildConfig.groovy
Hmm... I've reproduced the new failure with my test app (https://bitbucket.org/davidmc24/grails-page-resources-testapp). I think the other possible fix would be to ship the plugin as a binary plugin. I'm not going that way right now. I'll backout the change, add documentation about the ability to exclude the spring-webflow dependency, and push out a new release.