So, I took at look at Magellan’s dependencies.
Firstly, it seems that Magellan is actually part of the core Micro-Manager SVN repository. Sorry, I did not realize that. But it doesn’t appear to be distributed with the Micro-Manager download?
Anyway, I started trying to grok your dependencies. For me, the easiest way to do this is to Mavenize a project, so I started doing it:
It almost works, except for a couple of still-missing dependencies that I could not find:
ij3d.image3d. Any ideas where those live?
I already uploaded
1.4.22 (extracted from the official distribution) to the ImageJ Maven repository, so those dependencies are OK for now (if improper since they lack dependency declarations of their own).
But in order to guarantee reproducible builds, we will first need to cut a release version.
After going through all that, I have some misgivings about this plan. All of Fiji’s dependencies have been painstakingly organized over the past 2+ years as the project was Mavenized, and I don’t really like throwing a dirty project (incomplete dependencies) into the mix.
But I don’t have a concrete reason not to move forward, beyond the issue with the
ij3d.image3d packages. If we can sort those, we can go ahead and add Magellan as a dependency of BDV.
There is an open question whether you want Magellan’s other dependencies besides Micro-Manager itself to be uploaded to Fiji also. In particular,
commons-math (v2) is not currently on the Fiji update site.