[ImageJ-devel] [fiji-devel] Re: Permission to bump mpicbg.version to 2.0.0-SNAPSHOT?

[Johannes Schindelin]

Hi,

On Sun, 8 Jul 2012, Johannes Schindelin wrote:

> On Sun, 8 Jul 2012, Stephan Saalfeld wrote:
> 
> > To explain the mpicbg situation: I consider the version of the git
> > repository that is committed as submodule to the fiji repository the
> > stable release because I tested it in the full Fiji context (at least
> > for compiling issues) which includes TrakEM2 and ImgLib1/2.  That
> > version corresponds to what is uploaded to the Fiji updater.
> 
> Okay, that would be version 20120621, then, as that is the date of the
> commit in fiji.git, referring to the mpicbg commit 4200032831.
> 
> I verified that the Updater considers my compiled version of that
> revision and what you uploaded as identical, so I "deployed" (==
> "uploaded to the Maven repository" in Maven speak) the latter.

It turns out that I was able to fix the bug in MiniMaven which wanted to
use the old mpicbg version to compile blockmatching even when the
corresponding pom.xml clearly asked for the newer version.

This was possible due to the Mavenization of Fiji which allowed me to
import the Fiji Build project into Eclipse (after identifying a rather
serious problem together with Tobias Pietzsch on Friday, I was able to fix
the problem today, see the Git log for Fiji's src-plugins/pom.xml). Well,
part of it was helped by Eclipse, since I could not attach Eclipse to
Jenkins' Fiji Builds.

Anyway, the problem is a non-issue now, please disregard my original
request to bump scijava to a new version.

Ciao,
Dscho