[ImageJ-devel] Permission to bump mpicbg.version to 2.0.0-SNAPSHOT?
Johannes Schindelin
Johannes.Schindelin at gmx.de
Sat Jul 7 14:34:33 CDT 2012
Hi Stephan,
On Sat, 7 Jul 2012, Stephan Saalfeld wrote:
> On Sat, 2012-07-07 at 04:38 +0200, Johannes Schindelin wrote:
>
> > since mpicbg as of 20111128 is too old to compile (Mavenized)
> > fiji.git, may I bump it to 2.0.0-SNAPSHOT (which I uploaded manually
> > to imagej.snapshots)?
>
> Can you explain that to the non-expert?
The scijava POM:
https://github.com/scijava/scijava-common/blob/master/pom-scijava/pom.xml
is the intended parent POM for the scijava software stack. So basically,
every (Mavenized) sourcecode's top-evel pom.xml lists it as parent POM.
This is the case for ImgLib, ImageJ2, Bio-Formats, SCIFIO, and I probably
forgot a few. That POM lists a few Maven repositories and current versions
of components of the scijava software stack.
The current version for mpicbg is listed as 20111128, but I recently
uploaded a new artifact (manually, since mpicbg is not Mavenized) with the
version 2.0.0-SNAPSHOT. I needed to do that because parts of Fiji, in
particular blockmatching_.jar, require a newer version of that library.
Now, I do not foresee any conflicts introduced by pushing the mpicbg
version in the scijava POM to 2.0.0-SNAPSHOT, but as there are now
potentially many projects depending on scijava.pom, I want to play it
carefully.
Christian Dietz from the KNIME project already indicated privately that
they are unaffected by that version change.
Ciao,
Johannes
More information about the ImageJ-devel
mailing list