Bump pom-scijava to a SNAPSHOT version

The idea is to switch deployment to OSS Sonatype, and SNAPSHOT versions
will allow this developer to test the heck out of it.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Bump all plugin versions to the newest ones

As found out by running "mvn versions:display-plugin-updates", described
in

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

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
pom-scijava: Add a profile for deploying to OSS Sonatype

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

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Use pgp-maven-plugin instead of maven-gpg-plugin

The maven-gpg-plugin is waaaaay too inflexible for our needs. In
particular, it has only two modes to obtain the pass phrase for the
keyring -- both of them inconvenient: the interactive prompt will prompt
*everytime* something is signed (and in default mode, we will want to
sign the artifact, the javadoc, the sources, and of course .pom files
for all of them!) while the gpg-agent mode pretty much excludes headless
operation altogether -- and it is limited to a single keyring.

Instead, let's use the awesomeness that is Kohsuke Kawaguchi's work that
lets us specify the location of the key ring in those forms:

* current user's GPG info in $HOME/.gnupg/secring.gpg

	-Dpgp.keyring=keyring:

* different keyring:

	-Dpgp.keyring=keyring:keyring=path/to/keyring

* file exported via `gpg --export-secret-keys KEYID`:

	-Dpgp.keyring=keyfile:path/to/key.asc

Likewise there are multiple options for specifying the pass phrase:

* via command-line (unsafe):
	-Dgpg.passphrase=literal:<passphrase>

* via file (needs to take precautions to protect the file):

	-Dgpg.passphrase=file:path/to/textfile

* via gpg-agent:

	-Dgpg.passphrase=gpg-agent

Both keyring loader and pass phrase loader are actually *very* easily
customized: simply add a plugin dependency that has a class annotated
with @Component(role=PassphraseLoader.class,hint="file") similar to

	https://github.com/kohsuke/pgp-maven-plugin/blob/master/src/main/java/org/kohsuke/maven/pgp/loaders/FilePassPhraseLoader.java

Seeing how easy the pgp-maven-plugin makes things makes you wonder why
the Maven mavens did not get the memo and improved the maven-gpg-plugin
accordingly...

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Revert "Use pgp-maven-plugin instead of maven-gpg-plugin"

Unfortunately, the only released version of the pgp-maven-plugin
generates signature files with names incompatible with OSS Sonatype's
requirements.

This reverts commit 441befb57e1b4e7c9b02e8c17f9e92ea4f557ac5.

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>