MiniMaven repeatedly warns about mpicbg versions about fiji HOT 3 CLOSED

That is a big problem. It is a problem that is mainly due to axtimwalde/mpicbg#6 being ignored. Otherwise, we would have switched to using it everywhere (including TrakEM2 and Fiji) and the problem would be gone for good.

Background: due to the makeup of ImageJ 1.x' plugin class path, there can only be one version of any given artifact (otherwise there will be problems due to mismatching .class versions). Therefore, MiniMaven deletes other versions when it finds that it is asked to copy a dependency into jars/. Now, it does that every time it is asked to copy a dependency. That means that the plugins which depend (directly or transitively) on 0.6.1-SNAPSHOT make sure that previously copied version 20111128 gets deleted, and vice versa.

@axtimwalde did not tag a release version which is the reason we had to deploy version 20111128 as a work around. Unfortunately, the obvious fix never happened: to tag and deploy version 0.6.0.

As I stated above: this problem waits for axtimwalde/mpicbg#6 to be addressed (and that ticket was only opened after the request to tag a version went unaddressed for more than half a year).

I guess we could do the Fiji thing (i.e. getting things into a working state even if it requires ugly workarounds because a proper resolution turned out not to happen): I could simply hardcode an override of the mpicbg dependency version to 0.6.1-SNAPSHOT.

That would resolve this issue, of course, but sadly would also make every build involving the mpicbg dependency irreproducible. Which is ironic given the huge push by @axtimwalde at the high profile EuroBioImaging meeting in Barcelona 2012 (which is, after all, the reason why we worked so long and so hard to get all of the Fiji projects Mavenized).

I guess the next few days will show us what way to go.

from fiji.

Thanks for the e-mail. I auto-deleted GitHub messages for the last couple of days because I git auto-subscribed to an overwhelming number of messages that I didn't have time to process. Sorry.
In defense of why there is no release version of 0.6.0: It wasn't necessary nor sensible at the time. Today, it is hard to identify the point in time when mpicbg was at 0.6.0 and therefore I suggest that we label the current master as 0.6.1 release and set this as the first confirmed release version ever. Would that work?

from fiji.

The issue is almost gone; we just have to wait for the last user of a -SNAPSHOT version to get released. So I'll close this issue.

from fiji.