[
https://issues.apache.org/jira/browse/BATIK-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15415821#comment-15415821
]
Erich Schubert edited comment on BATIK-1005 at 8/10/16 7:24 PM:
----------------------------------------------------------------
Maven builds of Batik 1.7 are bad, unfortunately.
They do NOT include working codecs. The build ant script disabled building the
only working codecs in favor of some codecs not enabled.
The fixes for this bug has been a pull request on github for half a year, but
no reaction.
1. The maven package does not include imageio codecs:
https://github.com/apache/batik/pull/5
2. Alternative codecs are disabled, so they won't work either:
https://github.com/apache/batik/pull/6
3. The codec registry has a bug that often fails to register new codecs (more
precisely, it fails to revalidate the mime table):
https://github.com/apache/batik/pull/4
So even if the codecs were compiled (#1) and in the list (#2) they won't be
recognized as such, because of the registry bug (which is likely why someone
disabled them, causing #2 instead of fixing the registry bug).
All the fixes are very easy, but I have not seen any reaction so far,
unfortunately. It appears that Batik is pretty much abandoned.
Duplicate of: BATIK-1125 BATIK-1146 BATIK-1111 BATIK-818 (open for 8 years)
I wish someone with write access would just review and merge above three TINY
pull requests, and close all these duplicate bugs (up to "blocker" severity).
They are tiny tiny tiny patches (about 2 lines each) with a big big big
difference (working jpeg and png export).
was (Author: erich.schubert):
Maven builds of Batik 1.7 are bad, unfortunately.
They do NOT include working codecs.
The fixes for this bug has been a pull request on github for half a year, but
no reaction.
1. The maven package does not include imageio codecs:
https://github.com/apache/batik/pull/5
2. Alternative codecs are disabled, so they won't work either:
https://github.com/apache/batik/pull/6
3. The regsitry has a bug that often fails to register new codecs:
https://github.com/apache/batik/pull/4
So even if the codecs were in the list (and probably that is why they were
disabled as in #2!) they won't be recognized as such, because of the registry
bug.
All the fixes are very easy, but I have not seen any reaction so far,
unfortunately. It appears that Batik is pretty much abandoned.
> maven batik-awt-util 1.7 missing META-INF/services/ file for
> ImageWriterRegistry?
> ---------------------------------------------------------------------------------
>
> Key: BATIK-1005
> URL: https://issues.apache.org/jira/browse/BATIK-1005
> Project: Batik
> Issue Type: Bug
> Components: Utilities
> Affects Versions: 1.7
> Environment: Operating System: All
> Platform: Macintosh
> Reporter: Jessica
> Assignee: Batik Developer's Mailing list
>
> When we switched our project to maven, we started seeing a null pointer
> exception coming from the JPEGTranscoder, line 89. The exception happens
> because the singleton org.apache.batik.ext.awt.image.spi.ImageWriterRegistry
> instance does not have any ImageWriters registered so null is returned
> instead of a JPEGImageWriter instance.
> Looking at the code for the ImageWriterRegistry class, I think there should
> be a file called "org.apache.batik.ext.awt.image.spi.ImageWriter" inside of
> META-INF/services/ in the distributed jar which lists the image writers to
> register during setup. However, there is no such file in the
> batik-awt-util-1.7.jar.
> I do see a file in xmlgraphics-commons jar for the
> org.apache.xmlgraphics.image.writer.ImageWriter class, but the JPEGTranscoder
> doesn't use the registry from that package.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
