Remove unneeded dependency

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Adjust the project name

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Remove some sections from pom.xml to prepare for deploying to OSS Sonatype

In particular, we cannot have the pom-fiji-plugins parent (it is not
deployed to OSS Sonatype yet, it is at a SNAPSHOT version, and besides,
it is an inappropriate parent POM for JEP to begin with), we cannot have
<repository> entries except Sonatype itself, and we should not refer to
the imagej-maven-plugin anymore.

We also have to make the groupId and the dependency versions explicit
because they had been defined in the parent POM.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Adjust pom.xml in preparation for deployment

For deploying to OSS Sonatype, we need to have a license, a non-empty
description, a project URL and at least one developer.

We might just as well adjust the version and the correct groupId, too,
while we're at it.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Add common sections to pom.xml for deployment to OSS Sonatype

We will start deploying to OSS Sonatype (which is mirrored by Maven
Central, i.e. available without having to configure extra <repository>
entries in the pom.xml).

This project is not related to pom-scijava other than being used by
components in the larger SciJava ecosystem, therefore it would be
inappropriate to add pom-scijava as a parent. However, we can copy the
relevant parts of pom-scijava (https://github.com/scijava/pom-scijava),
and that is exactly what this commit does.

It also adds the section declaring that we want to use the
nexus-staging-maven-plugin, to offer a cherry-pickable changeset for
other, similar projects we want to deply to OSS Sonatype.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Bump to next release cycle

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