Thomas Müller wrote:
Hi,
I am for using Java 1.5.
+1 for me.
Another option would be to switch to Java 1.5 and provide some
documentation or a build profile that uses Retroweaver if Java 1.4 is
still required. I have never used it and I don't have an opinion on
it, just to list the option: http://retroweaver.sourceforge.net/
We've used retroweaver on ESOE (http://esoeproject.org) quite
successfully and it is quite a complex code base including lots of JAXB
generated stuff. Didn't really have any troubles with it and works well
for the clients.
Bradley
Regards,
Thomas
On Wed, Jun 25, 2008 at 12:21 PM, Jukka Zitting <[EMAIL PROTECTED]> wrote:
Hi,
Sun's Java 1.4.x is reaching EOL status in October, so I was wondering
if there's still need for us to continue using Java 1.4 as the
baseline for Jackrabbit. Upgrading the minimum platform requirement to
Java 5 would give us a) some nice language features, b) the chance to
drop the concurrent library dependency, and c) the chance to directly
use libraries like Apache Tika that are based on Java 5.
Are there good reasons for sticking with Java 1.4? IMHO a natural
upgrade point to Java 5 would be Jackrabbit 2.0.
BR,
Jukka Zitting
