Use pom-scijava to get proper versions of openmicroscopy software

[LeeKamentsky]

Dsco says the following and it shall eventually be so:
Johannes Schindelin
1:47 PM (7 minutes ago)

to me, ImageJ
Hi Lee,

On Wed, 19 Mar 2014, Lee Kamentsky wrote:

So far, I use a version in my own POM to keep things from shifting when I
don't expect them to. At some point, I might let it float with the
snapshots and fix it to a particular release when I tag, but not yet.

Well, if you use pom-scijava, you only need one such number. In the
current case, that would be 1.150, just released, including the bump to
the new ImageJ release.

Ciao,
Dscho

[ctrueden]

To be clear: pinning to a particular pom-scijava just lets you inherit a bunch of (intended to work together) versions of various artifacts, both as version properties, and someday soon also as pluginManagement declarations. You won't be pinning to SNAPSHOTs by using it. The only way to pin to SNAPSHOTs is to do it really explicitly by either: A) overriding one of the foo.version properties to point to a SNAPSHOT; or B) directly change the <version> of a dependency declaration to point to a SNAPSHOT.

[LeeKamentsky]

Thanks, Curtis. Snapshots are sort of a moot point at present - I'll probably stick with versions supplied by pom-scijava for the next 6 months. I've switched to pom-scijava v 1.150 for CellProfiler. That's probably the target for our upcoming patch release.

[ctrueden]

@LeeKamentsky: Cool, definitely let us know if you have any problems with it.