pom-scijava: Add the OSS Sonatype repositories

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
White-space fix

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Add an <scm> section to pom-scijava, required by the release plugin

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Use the nexus-staging-maven-plugin for deploying

As described in

http://blog.sonatype.com/2013/09/simplified-releases-to-the-central-repository-with-nexus/

Unfortunately, the nexus-staging-maven plugin's version 1.5.1 requires
Maven 3.0.4 -- while we want to require 2.2.1 in general instead -- and it
is not possible to override the minimally-required Maven version in a
profile, not even by using a property in the <prerequisites> section. For
now, we just have to live with 'mvn versions:display-plugin-updates'
complaining about that...

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Fix release:prepare not committing the version into the tag

This was suggested in http://stackoverflow.com/a/20657721

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Revert "Fix release:prepare not committing the version into the tag"

Actually, even with this work-around, this developer was not able to
convince 'mvn release:prepare' to actually commit the *release* version
to the pom.xml file before tagging it.

It did not even work when downgrading maven-release-plugin to version
2.4.1 as suggested here: http://stackoverflow.com/a/15737902

A pity, because the maven-release-plugin would be real nice to use
(iff it worked properly).

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Bump pom-scijava to 1.117-test to test deploying to OSS Sonatype

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Add license/developers section, required by OSS Sonatype

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>