https://issues.apache.org/bugzilla/show_bug.cgi?id=49703
--- Comment #4 from Jeremias Maerki <[email protected]> 2010-09-02 11:20:28 EDT --- I must say I'm not too happy with the idea of introducing multiple classes to handle a deprecation from almost two years ago (https://svn.apache.org/viewvc?view=revision&revision=718586) for an interface that has probably never been used directly outside of the XML Graphics project. Essentially, you're removing the deprecations completely. Without actually searching through the source code, the user won't find out anymore if he's working with a deprecated method. We've had a release in between, so why not just remove this method? This is very technical stuff (i.e. not an end-user API) and we can expect people to migrate within 2 years should anyone have used it. But yes, freely upgrading xmlgraphics-commons.jar while staying with an older fop.jar will cause problems then. But at some point, deprecated stuff should be removed. A similar argument for the "old" PDF/A identification URI. We're mostly about producing PDF here, not about reading it. So if anyone needs to process outdated PDF/A files they can recover the old PDF/A schema from out Subversion repo or write their own. At any rate, the old (wrong) URI should not be used anymore for new PDFs. I've locally applied the patch and did the following changes to it: - @asf.todo converted to //TODO comments - Removed "old" PDF/A identification URI (deprecated) - Removed org.apache.xmlgraphics.java2d.TextHandler.drawString(String, float, float); (deprecated) -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
