Commented-out classifier in components.xml (#35)

It turns out the Maven Source Plugin doesn't like it if the main
artifact has the empty string as its classifier.  It will fail printing
a warning saying "NOT adding sources to artifacts with classifier as
Maven only supports one classifier per artifact.  Current artifact
[xxxxx] has a [] classifier."  Apparently the classifier needs to be
`null`, which means leaving off the `classifier` tag altogether in
'components.xml'.  We comment-out the tag and include a reference to the
issue so we know why we did it.
Merge pull request #36 from adbrown85/35

Commented-out classifier in components.xml (#35)
README.md: Do not refer to SciJava as a "fork"

Yes, it is a GitHub fork, but not a diverging fork in that the SciJava
releases are simply cut from the latest master branch, with no patches.

The main reason for the "fork" now is as a place to put release tags.
README.md: add another working example

Thanks to Matt Gumbley of DevZendo.org for the reference!
README.md: remove bogus HTML tag
README.md: add SLIM-curve working example
Reflect the change of the repository name

This assumes that the pull request will be merged just before or after
renaming the repository from 'maven-nar-plugin' to 'nar-maven-plugin'
as per the convention that 'maven-*-plugin' names are reserved for
the special plugins that Maven Central controls.

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

In the same spirit as renaming the plugin from 'maven-nar-plugin'
to 'nar-maven-plugin' as per the convention that only Maven Central
plugins should follow the 'maven-*-plugin' (some plugins are more
equal than others), we also follow the convention to use a groupId
that we 'control'.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Use non-infringing language for plugin name

We are supposed to call it the "NAR plugin for Maven" or
(less ideally but shorter) the "NAR Maven plugin".

For details, see this message from the maven-users list:
http://mail-archives.apache.org/mod_mbox/maven-users/201306.mbox/%3CCA%2BnPnMzeORcpFL8gGq%3DycKFgSE-5WzBHM8PuvX-NZqOBEF6J0A%40mail.gmail.com%3E

The most relevant paragraph is:
> The allowed pattern of usage is that where the use of the mark is
> referring to the plugin being for use with Maven, hence "___ Plugin
> for Maven" is fine but "Maven ___ Plugin" is not. Obviously "___'s ___
> plugin for Maven" is even better, e.g. "Mojo's Cassandra plugin for
> Maven" (which has the bigger fun of using two Apache marks...)

We still need to "git grep 'Maven NAR'" the codebase and replace all
such language with the language mentioned above, instead.
Complete the 'Maven NAR' -> 'NAR Maven' renaming

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Change groupId to com.github.maven-nar

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

Since '-' is not a valid part of a package name, we use
com.github.maven.nar instead of com.github.maven-nar.

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