Phase out ImgLib1
dscho opened this issue · 4 comments
As agreed between @tpietzsch, @StephanPreibisch, @ctrueden, @hinerm and myself at the ImgLib2 hackathon in May 2013, ImgLib1 is deprecated. Therefore it makes the opposite of sense to release it now. Corollary: Stitching must rid itself from the dependency to be able to be built reproducibly.
This is required before Stitching can re-enter pom-fiji.
I disagree with not `releasing' ImgLib1. I made my opinion clear in another thread and in discussions in October 2014. I disagree that making a non-SNAPSHOT, though deprecated, jar available for legacy compatibility would send confusing signals to anybody. Not doing so hinders progress on other projects for dogmatic and irrelevant reasons.
I agree with @axtimwalde, but am willing to compromise if we can find an alternative that @dscho likes and does not hinder progress. @hinerm and I are currently upgrading the whole set of Fiji projects to the latest pom-fiji which includes the ImgLib2 release version. We will address legacy-imglib1 at the end of that process.
@StephanPreibisch To help with this, I pushed an update to the latest pom-fiji parent, along with some associated POM cleanup: a5c833e
However, I did not address the usage of ImgLib1. As @dscho says, if you have time to address this, that would be fantastic.
Or if you do not have time to do it, please let us know.
P.S. To build the code from the CLI, you can use the invocation:
mvn -Dscijava.enforce.skip