Seeing how a plugin-parent module might be used to simplify/unify plugin build configurations.
notes
more comments
more comments
kill comment
notes
Update pom, use maven 3 deps.
Do not include scope, for -compile.pom scope=compile is the default.  For -dependencies.pom, adding scope=provided to DM entries adds downstream complication to fix the scope as needed.
Some clean up.
Update provided-dependencies-maven-plugin to 1.6-SNAPSHOT.
Generate a -dependencies.pom for nexus-plugin-api so we can import it in plugin-parent.
More notes.
nexus-web-utils is provided by nexus-plugin-api
Forgot type=pom on scope=import
Use plugin-parent
kill cruft
Generate -dependencies.pom for nexus-plugin-test-api, include that in plugin-parent.
Add plexus-jetty-testsuite to nexus-plugin-test-api.
Update rrb plugin to use plugin-parent.
Add nexus.version property to plugin-parent.
Update mac plugin to use plugin-parent.
Update maven-bridge plugin to use plugin-parent.
Fix up groupIds
Use plugin-parent for restlet1x
Flip indexer bits to use plugin-parent
Trying to get ldap plugin using plugin-parent
Another refinement of plugin-parent, avoid scope=import... its a fucking shit half-ass functional feature.