-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
javax.media:jai_imageio:1.1 FAILED #64
Comments
This dependency on jai_imageio has long been bothering me and I have been trying to finish my own TIFF decoder for a very long time. Unfortunately I have been too busy to finish this. As a result, ICAFE itself cannot handle all/most of the tiff variations so for the time being, we still have to rely on third party library to read TIFF. I took a look at the links you put and maybe the fork (new package) will work. Will have to test it later sometime. |
I switched to the JBoss version for the time being, which passed my basic jpeg->tiff test. |
Did you read jpeg and save to tiff? That will not need the library at all. Reading jpeg is using basic ImageIO and saving to tiff is using icafe. The library is only needed when reading tiff. |
Oh sorry, my use-case is only to write multi-page TIFFs for customer integrations. I tweaked the test a bit to read from a TIFF file and it worked. So promising workaround until you have a preferred solution. |
Is there a way i can get the required jars so that i can manually import them for the time being..? |
@abdullaunais are you referring to the imageio jar? it is located in the lib folder. |
Oh. found it. thanks. |
I believe since Java 9 there is native TIFF support. Another option might be the TwelveMonkeys library which "is a collection of plugins and extensions for Java's ImageIO." |
Due to
maven.geotoolkit.org
being down, this dependency cannot be resolved. It might be worth using the dependency from a more reliable repository, such as Central. That version, sadly, does not include the jar. There a release on JBoss' though.There also appears to a fork (new package) that is being maintained. Perhaps that would be useful for bug fixes and being available on Central and JCenter.
The text was updated successfully, but these errors were encountered: