[ImageJ-devel] [fiji-devel] ImgLib2 merge to master

[Stephan Saalfeld]

Hi,

thanks for putting your hands into this.  As Curtis has explained
already, the idea is to skip the non-compiling sub-projects from the
builds into a running system.  Thanks to Curtis and the ImageJDevs who
have circumvented a terrible bug in javac, these sub-projects are:

imglib2
--> core
--> io
--> ui

ImgLib1 as required for Fiji is entirely unaffected and compiles
bravely, just lives in another place.

That should be possible in the Fakefiles---not?!  Should I have a look?

In opposition to your workflow, we found it helpful to leave broken code
broken instead of break-fixing it into compiling but not functional
state until somebody runs into the trap (TODO comments are less hintful
than compile errors).  Eclipse allows us to do that and we are
thankfully using this opportunity.

Cheers,
Stephan




On Thu, 2011-04-21 at 10:59 +0200, Johannes Schindelin wrote: 
> Hi,
> 
> On Thu, 21 Apr 2011, Johannes Schindelin wrote:
> 
> > On Wed, 20 Apr 2011, Curtis Rueden wrote:
> > 
> > > 1) Update Fiji Fakefiles to reflect the new directory structure above.
> > 
> > I just pushed a fix to Fiji's 'imglib-split' branch. imglib2-algorithms, 
> > imglib2-ij (and as a consequence, imglib2-scripting) and imglib2-ops do 
> > not compile yet.
> 
> To clarify: I did not yet merge to Fiji's 'master' branch because I am 
> unsure what you guys intend to do about the compile errors. If they are 
> there to stay for a while anyway, I'd just as well merge now.
> 
> If I (or for that matter, others) would have been given the information, 
> and thereby the chance, how to migrate code, the compilation would 
> probably not be in such a desastrous stage only Eclipse users could 
> possibly love.
> 
> Ciao,
> Dscho
>