#2 modules-parent: move plugins to ease pom refactoring

[Alberto Gallardo]

The current modules-parent pom (as for today, 1.3-SNAPSHOT) downloadable:
http://bp-cms-commons.svn.sourceforge.net/viewvc/bp-cms-commons/opencms_commons/modules/modules-parent/trunk/pom.xml?view=log
has many plugins under build/plugins that could be moved to build/pluginManagement.

I have several opencms artifacts created with the archetype opencms-module-archetype. I need to refactor their poms, so I don't need to redefine project properties everywhere. My current project dependency diagram looks like this:

modules-parent <---- my-common-config <---- my-module-1
modules-parent <---- my-common-config <---- my-module-2
modules-parent <---- my-common-config <---- my-module-3
(etc)

Currently, the 'maven-dependency-plugin' plugin belongs to the build/plugins section. This means that, if I install 'my-common-config', it unpacks the opencms-webapp war.

This plugin could be moved to build/pluginManagement. It'd also be convenient to move the rest of the plugins from build/plugins to this build/pluginManagement.