nan21/nan21.dnet.core — pull request #3 by topping (2012-07-18 12:17:46+00:00)
Title: Clean up maven build

It looks like there are a lot of changes here, but there really aren't... I've made these changes both in core and in modules.

* Restructure the code by merging the *.parent modules with the root module of a given directory. This simplifies the chain for Maven 3, which now works.
* Make the projects inherit from their respective parent projects. This allows consistent use of things like repositories, which are important for making sure dependencies are found.
* I have repeatedly deleted the local repository and rebuilt to make sure that the build is portable to anyone's machine and will not fail because a dependency could not be found.
* With a complete POM hierarchy, moved plugins that are used everywhere to the top-level builds and disabled them where appropriate (i.e. bundlor).
* Extract Spring version to a property so it can be updated more easily.
* Move maven-jar-plugin and maven-war-plugin to elements at the top level. In effect, this says "if this plugin is going to be used, use these settings, otherwise do not run the plugin". Since all of the projects that are jar or war type use these plugins, the correct configuration is automatically applied from the top level.
* Move the maven-source-plugin, maven-compiler-plugin to the top level. These can run everywhere without harm.