Create a parent POM.

This POM
* sets the current version for all standard plugins and configures
* provides configuration for a two step release
[maven-release-plugin] prepare release lib-parent-1
[maven-release-plugin] prepare for next development iteration
Define plugin versions at plugin management.

The versions are not inherited if they are defined in the
`build/plugins` section.
Add missing plugins that are defined by super POM.

* maven-compiler-plugin
* maven-jar-plugin
* maven-resources-plugin
Sort plugins alphabetically.

Seems to be a natural ordering.
Add missing plugins that are defined by oss-parent

* maven-enforcer-plugin
* maven-release-plugin
Set current versions for plugins.
[maven-release-plugin] prepare release lib-parent-2
[maven-release-plugin] prepare for next development iteration
Set current versions for plugins.

maven-clean-plugin ..................................... 2.6 -> 2.6.1
maven-compiler-plugin .................................... 3.1 -> 3.2
maven-surefire-plugin .................................. 2.17 -> 2.18
org.sonatype.plugins:nexus-staging-maven-plugin ...... 1.6.4 -> 1.6.5
[maven-release-plugin] prepare release lib-parent-3
[maven-release-plugin] prepare for next development iteration
Use Flatten Maven Plugin.

This plugin generates a flattened version of the `pom.xml` and makes
maven to install and deploy this one instead of the original
`pom.xml`. The flattened POM doesn't contain useless information like
dependencies with scope `test`. Hence the customer doesn't have to read
information that he doesn't need.
[maven-release-plugin] prepare release lib-parent-4
[maven-release-plugin] prepare for next development iteration