Hi everyone,
> I think we have to be pragmatic about that. This issue has been > outstanding for more than 2 months and hasn’t been dealt with yet. That > means that among the current team nobody has the knowledge or the time > to handle it. I have neither of those. I've made partial testing (in the scope of Batik bug 46513 [1]) and I've notice some visual regressions in a test regard run. Nevertheless, I currently also lack time for a deeper understanding of what's happening/fixing stuff/committing changes. Generating a patch to that bug (with the required changes, textually describe in the bug) would at least be a good idea. :-) > Constantly getting Gump warnings is not only annoying, it’s also > dangerous as we may miss things that break in other areas of the code. I'd say one of the not-dangerous-but-yet-very-important-IMO is not being compatible with most OSS distributions due to not using imageio. I guess failing to solve this issue we're forcing people to stick with Sun (errr, Oracle) and I guess that somehow goes against the ASF philosophy... Right? > So I’d go for any of the solutions below that is the quickest to > implement. If the loss of functionality that results of it really annoys > some users, they are free to step up and provide a better fix. I agree on this. I'd expect other Batik developers would engage with work as well (specially Thomas, probably the most experienced Batik developer in this matter), but I'd go for simply breaking things a bit (by "short-circuiting" the proprietary classes), adding documentation in the site/leaving the previous code/configuration commented and let people affected to step in (for help). :-) > After > all, that’s how open source works, isn’t it? Yyyyyyup! ;-) Cheers, Helder [1] https://issues.apache.org/bugzilla/show_bug.cgi?id=46513 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
