Ask m2e nicely to do what we continue to need

Probably we want that in scijava's pom. It forces m2e to run the
buildnumber plugin -- if that plugin is configured -- and to package
.jar files, however m2e might kick and scream foul.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
MiniMaven: write the manifest to target/classes/

... rather than making it on the fly when writing the .jar file. This is
more in line with how Maven works...

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
MiniMaven: special-case the Fiji Updater

Since the original Fiji Updater checksummed the contents of the .jar files
byte for byte, output from Maven was considered different with every new
build. For this reason, the ImageJ Updater special-cases a couple of file
types and skips e.g. the timestamps in .properties files.

Since we would like the original Fiji Updater to update itself, at least,
and since it verifies the checksum of the downloaded file, we need to make
sure that the file Fiji_Updater.jar does not contain such fiddly files.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Updater: add some functions to access the ImageJ Updater

This is the first commit to finish the move of the Fiji Updater into the
code base of ImageJ2.

The idea: Fiji will transparently hand off to the ImageJ Updater as
included in ImageJ 2.0.0-beta3.

We will keep the Fiji Updater as this rudimentary ImageJ1 plugin which
knows only to run the ImageJ Updater, and how to load it from the Update
Site of ImageJ2 if it is not available locally yet.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Updater: add more functions to access the ImageJ Updater

We would also like to let it handle the up-to-date check.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Special-case the first ImageJ Updater run

We want to yse the ImageJ Updater which recently has been forked off of
the Fiji Updater with the idea to move the component to ImageJ2. But that
means that we want to access the ImageJ Updater from within Fiji without
having its sources anymore.

So the idea is to instantiate the Updater itself from a known-good version
on the ImageJ Update site and let it install the ImageJ Updater. After
that, we use the ImageJ Updater happily ever after.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Refactor the ImageJ Updater Adapter

Let's separate the part specific to ImageJ 1.x from the part that is
specific to accessing the ImageJ Updater (part of ImageJ2). This will
allow us to add back the command-line interfaces of the Fiji Updater
(which will ask ImageJ Updater to do the job, just like the Fiji Updater
GUI will).

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Updater adapter: add a stderr-based user interface

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Updater: also access ImageJ2's command-line Updater

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Bug Submitter: use the new functions of the ImageJ Updater

The Fiji Updater is dead. Long live the ImageJ Updater!

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Package Maker: use the new functions of the ImageJ Updater

The Fiji Updater is dead. Long live the ImageJ Updater!

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Update Fiji: Use the ImageJ Updater

Let the two plugins and the two command-line interfaces we provided in the
Fiji Updater call the ImageJ Updater instead.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Update calculate-checksums.bsh to use the ImageJ Updater

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Updater: support ./fiji --update gui

This is new now, and possible only due to our way of accessing
ImageJ's Updater.

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