Hi Jonas, > I am unable to import files with LOCI, no matter which loci-jar is > deleted or not...
I updated Fiji with the 4.4.5 release of Bio-Formats last night, so these errors are almost certainly my fault. Unfortunately, I am unable to replicate the problem. I tried updating an existing Fiji on another workstation, and all worked fine (though I did have to click "break the dependency" in response to one prompt). I also tried with a fresh continuous release downloaded from fiji.sc just now, and it also worked. If you run Help > Update Fiji, click on Advanced mode, what do you see for "Locally modified files" and "Uninstalled files only"? A fully up-to-date Fiji should not have any entries. -Curtis On Tue, Dec 11, 2012 at 6:31 AM, <[email protected]> wrote: > Hi! > > I am still having difficulties with the latest Fiji (both w/w/out jre) and > LOCI. Receiving same errors as described above. > > As of now I am unable to import files with LOCI, no matter which loci-jar > is deleted or not... > > Have I magically jinxed my Fiji folder (again) or is this a problem shared > by others? > > Awesome work btw, Johannes (: > > //Jonas > > On Wednesday, August 1, 2012 7:37:26 PM UTC+2, Johannes Schindelin wrote: > >> Hi Sebi, >> >> On Wed, 1 Aug 2012, [email protected] wrote: >> >> > I tried to download the most up-to-date version ( >> > http://jenkins.imagej.net/job/**Stable-Fiji/** >> lastSuccessfulBuild/artifact/**fiji-nojre.zip<http://jenkins.imagej.net/job/Stable-Fiji/lastSuccessfulBuild/artifact/fiji-nojre.zip>) >> >> > >> > >> > This contains the loci_tools.jar as well as the the individual jars. So >> > should i just delete which files? This issues is quite critical for us, >> > since the Loci Bio-Format import is cruicial for us (and customer) to >> > import the OME-TIFF data produced by our imaging software. >> >> Yes, it is safe to delete loci_tools.jar. My work last year on enabling >> multiple update sites introduced the bug that removing files from update >> sites does not mark them as obsolete if you updated the files >> successfully >> before. We just did not hit that bug because we did not remove files in a >> long time ;-) >> >> > Do you still have an idea when this problem might get solved? >> >> It is fixed in the source code, I just have to upload a new version (for >> which I need to be comfortable with the current state first, though ;-). >> Should be happening within the hour. >> >> Ciao, >> Dscho >> > > _______________________________________________ > ImageJ-devel mailing list > [email protected] > http://imagej.net/mailman/listinfo/imagej-devel > >
_______________________________________________ ImageJ-devel mailing list [email protected] http://imagej.net/mailman/listinfo/imagej-devel
