This is a bug mostly to be used as a placeholder or, as suggested [1], as a tracking bug. Idea was to start accepting issues which are specific to versions above Java 1.4 and use this issue as a blocker. This also seems the proper place to attach patches which help accomplishing the task (of dropping Java 1.4 support). Marked Batik version 1.8 as the version where this is experienced, although it would be more natural to mark as a "Target Milestone" instead (which currently has no items). Side note: if "Target Milestone"s are to be created, I'd suggest at least two items: "1.8" (next release as of this writing) and "next"/"future" or similar to mean an unscheduled/unplanned release somewhere in the future. [1] https://issues.apache.org/bugzilla/show_bug.cgi?id=45397#c1
That can be read like there are already efforts underway to remove Java 1.4 support. With my PMC chair hat on, I want to make it clear that such a move should not be done before an informed decision has been reached by the committers. And to date, this was not the case. I'm writing this just in case anyone panicked after reading about dopping Java 1.4. :-)
(In reply to comment #1) > I'm writing this just in case anyone panicked after reading about dopping Java > 1.4. :-) Oops, sorry! Of course this was not my intention. ;-) Yes, this will likely take some time, even if the EOL period for the (Standard Edition) has already been reached [1] a couple of months ago. Idea was just to allow some sort of tracking for this future action. The text in comment 0 somehow states that, although probably I should have made it more clear. Thanks for clearing that up. :-) [1] http://java.sun.com/j2se/1.4.2/
See a tightly related thread, "Switching to Java 1.5", occurring in general@ [1]. [1] http://mail-archives.apache.org/mod_mbox/xmlgraphics-general/201010.mbox/browser#msg-36
(In reply to comment #3) > See a tightly related thread, "Switching to Java 1.5", occurring in general@ > [1]. > > [1] > http://mail-archives.apache.org/mod_mbox/xmlgraphics-general/201010.mbox/browser#msg-36 IMPORTANT: A vote is now underway in general@. I'd urge other Batik developers to participate ASAP: http://mail-archives.apache.org/mod_mbox/xmlgraphics-general/201010.mbox/browser#msg-51 Also, increasing importance due both to the relative priority and to the voting process as well.
As a side note, I guess we should probably make sure to release Batik 1.8 before this move: the currently released version (Batik 1.7) has Java 1.3 as minimum requirement and jumping to Java 1.5/1.6 in the following release just seems too much. (It's probably a shoot in the foot, we might lose some users without any specially relevant benefit.) WDYT?
(In reply to comment #4) > IMPORTANT: A vote is now underway in general@. I'd urge other Batik developers > to participate ASAP [...] UPDATE: voting has ended and it passed, which means we "fix" this whenever we want. Nevertheless, I'm decreasing priority again, as IMHO this should be handled only _after_ the 1.8 release (see comment 5) - I'm creating a thread in Batik users to have a better information basis to evaluate this. [1] http://mail-archives.apache.org/mod_mbox/xmlgraphics-general/201011.mbox/browser#msg-12