Mark Stephens

Mark Stephens has been working with Java and PDF since 1999 and has diversified into HTML5, SVG and JavaFX.

He also enjoys speaking at conferences and has been a Speaker at user groups, Business of Software, Seybold and JavaOne conferences. He has a very dry sense of humor and an MA in Medieval History for which he has not yet found a practical use.

Which legacy versions of Java should we support for our PDF library

28 sec read

There is always a delicate balance between backwards compatibility and progress. At the moment, we support Java 1.4 and above for our PDF library.

Java 1.4 came out it 2002 and Java 1.5 appeared in 2004. Java 1.5 included a number of useful changes so we would like to make this the legacy version we support.

With the Java world is now moving towards release 1.7 next year and NetBeans is already offering support for it. Dropping 1.4 support would mean we support Java 1.5, Java 1.6 and Java 1.7

We are not aware of any clients who desperately need 1.4 support and it seems a suitable time to make the change and embrace the changes in the Tiger release.

Does anyone feel differently? Please let us know. Otherwise today’s release will be the last 1.4 compatible update and we will make 1.5 the minimum requirement for JPedal.

Mark Stephens

Mark Stephens has been working with Java and PDF since 1999 and has diversified into HTML5, SVG and JavaFX.

He also enjoys speaking at conferences and has been a Speaker at user groups, Business of Software, Seybold and JavaOne conferences. He has a very dry sense of humor and an MA in Medieval History for which he has not yet found a practical use.

Leave a Reply

Your email address will not be published. Required fields are marked *