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

[Stephan Saalfeld]

Hi Albert,

as Steffi pointed out, you are missing dependencies as is shown in the
Problems window.  You may not see detailed compile errors before the
project settings are reasonably in place.  In the left tab, you have
been diving into the file tree instead the source package tree which is
on top and closed.  Have you imported the project using Maven?

Best,
Stephan




On Thu, 2011-04-21 at 14:37 +0200, Albert Cardona wrote: 
> 2011/4/21 Stephan Preibisch <preibisch at mpi-cbg.de>:
> > Hi Albert,
> >
> > sometimes Eclipse gets stuck as you described. What always worked for me is
> > to recompile it for Java5, which really forces him to recompile everything
> > and afterwards go back to Java6 ... you find it in Project -> Properties ->
> > Java Compiler
> >
> > Sometimes there are also simply some jar files missing, check the "problems"
> > tab for that ...
> 
> 
> I tried the java 6 to 5 change, and then also looked into the problems
> tab. Nothing looks conspicuous. I am attaching a screenshot. Notice
> how the package list shows as hierarchical instead of flat for some
> reason despite the setting to "Flat".
> 
> Please let me know if anything stands out as the obvious problem.
> 
> Albert
> 
> >
> > Bye bye,
> > Stephan
> >
> > -----Original Message-----
> > From: imagej-devel-bounces at imagejdev.org
> > [mailto:imagej-devel-bounces at imagejdev.org] On Behalf Of Albert Cardona
> > Sent: Thursday, April 21, 2011 11:43 AM
> > To: Stephan Saalfeld
> > Cc: Imagejdev.org Developers; Fiji developers
> > Subject: Re: [ImageJ-devel] [fiji-devel] ImgLib2 merge to master
> >
> > 2011/4/21 Stephan Saalfeld <saalfeld at mpi-cbg.de>:
> >> 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.
> >
> >
> > Eclipse shows an exclamation sign on the imglib project node and gives
> > up completely on indicating where there are errors.
> >
> > Is there any way to make eclipse behave? I would like to fix
> > imglib2-scripting and I have no idea where to start. The first problem
> > is that some key imglib2 classes have disappeared, such as ImgCursor.
> > The documentation that Johannes was asking for would go a long way.
> >
> > Albert
> >
> > --
> > http://albert.rierol.net
> >
> > _______________________________________________
> > ImageJ-devel mailing list
> > ImageJ-devel at imagejdev.org
> > http://imagejdev.org/mailman/listinfo/imagej-devel
> >
> > --
> > You received this message because you are subscribed to the Google Groups "Fiji-devel" group.
> > To post to this group, send email to fiji-devel at googlegroups.com.
> > To unsubscribe from this group, send email to fiji-devel+unsubscribe at googlegroups.com.
> > For more options, visit this group at http://groups.google.com/group/fiji-devel?hl=en.
> >
> >
> 
> 
>