Moving the new manifest publishing features to the nebula-publishing-plugin
Identify two bugs with non-runtime confs
Rename nebula-developer plugin (name too broad)
Don't make our own mavenLocal repository
Be more intelligent with when to sign artifacts
Merge remote-tracking branch 'origin/master' into feature/publish-manifest

Conflicts:
	build.gradle
Merge pull request #10 from nebula-plugins/feature/publish-manifest

Publish manifest information to Maven pom
Hold back plugin-plugin
Merge remote-tracking branch 'origin/master' into remove-maven-local-publishing
Setup NebulaSignPlugin to be testable with task graph
Merge pull request #16 from nebula-plugins/remove-maven-local-publishing

Remove maven local publishing
[Gradle Release Plugin] - pre tag commit:  '1.12.7'.
[Gradle Release Plugin] - new version commit:  '1.12.8-SNAPSHOT'.
Have publishing plugin reference info and contacts plugin
Merge pull request #17 from nebula-plugins/use-pom-developer-plugin

Have publishing plugin reference info and contacts plugin
Merge branch 'gradle-1.12' into resolve-across-configurations

Conflicts:
	src/test/groovy/nebula/plugin/publishing/maven/ResolvedMavenPluginIntSpec.groovy
Sorta ugly hack to dump non-runtime dependencies into pom file. It doesn't deal with scope mappings.
More messing conf mapping like stuff, to include web app dependencies
Make sure there is only one dependencies block
Merge pull request #18 from nebula-plugins/resolve-across-configurations

Resolve across configurations