Closed haesleinhuepf closed 6 years ago
@haesleinhuepf Sorry this slipped through the cracks.
Do you still experience this issue? Or was it transient? Please close this issue if the problem no longer happens.
FWIW, that error message indicates some version skew due to some recent(ish) Bio-Formats library renames. But I didn't know such problems hit the Java-8 update site directly. It was only a problem (to my knowledge) when the Bio-Formats update site was enabled. And that should also be fixed now.
The issue still exist when I try to compile latest Fiji jars with my program and new ImageJ() causes the problem. I do not need bioformat . What I have to delete? Deleting bio-formats folder does not help!
@Claus1 This is not the same issue. What you are talking about is something from a development environment, no? Whereas this issue was about the binary Fiji distribution not working out of the box. Please post your question on the ImageJ Forum and be specific. See Bug reporting best practices for tips on how to write a good bug report.
What you are talking about is something from a development environment, no?
I think no. I try to use jars from Fiji and they work wrong. ImageJ = new ImageJ() causes the same issue with
java.lang.IllegalArgumentException: Invalid service: io.scif.ome.services.Defaul tOMEMetadataService at org.scijava.service.ServiceHelper.createExactService(ServiceHelper.ja va:280)
Pure ImageJ 2 rc46 binary installation from the site works ok. Only. Newest binary versions ImageJ from maven reps do not process correctly (2.0.0-rc-65) because it has some jars references from unknown libraries. That references obviously exist in maven repos but with slightly different names. It seems like nobody supports it and checks.
@Claus1 Happy to help if you post your question on the ImageJ Forum. Again, please describe exactly what you are trying to do. From your writeup above, I do not understand exactly what you are trying to do, or how you are attempting to do it. I do actively support the core ImageJ libraries and the newest ones should definitely be working, provided you are deploying the JARs as intended.
Again, please describe exactly what you are trying to do.
I try to use ImageJ from my program for filtering images without GUI. Using jar files from latest Fiji is not possible for that because the initialization issue above. May be it is wrong way to use ImageJ but binary reference in my project
is not resolved if I use instructions from the site. Some referenced libraries are uknown for "Maven repo" at "http://repo1.maven.org/maven2", "Spring repo" at "http://repo.springsource.org/libs-release", "Apache repo" at "https://repository.apache.org/content/repositories/releases", "JBoss repo" at "http://repository.jboss.org/nexus/content/groups/public-jboss", "Sonatype repo" at "https://oss.sonatype.org/content/repositories/releases", "Mvnrepository" at "http://mvnrepository.com/artifact"
Make clean project with this dependency and will see.
@Claus1 Sorry that replying to this fell through the cracks for me.
From your list above, what is missing is the ImageJ Maven repository! https://maven.imagej.net/
A lot of the core ImageJ libraries, including net.imagej:imagej
, are located in this repository. You need that repository in your pom.xml
or similar build file for whatever build system you are using.
If you still need assistance, please push an MCVE somewhere public so that we can see exactly how your project is set up, and determine in detail what is going wrong.
is not resolved if I use instructions from the site.
Which instructions? Link, please.
@ctrueden I avoided the issue by making jars from Fuji sources.
Hey guys,
I just downloaded a fresh Fiji. When starting it, it closes after some seconds. When running it as debug.exe, it says
May there be a quick solution available - like jumping back to a former version of the installer? Just to make the downloaded Fiji work again until this bug is fixed?
Cheers, Robert