By utakapp
via jroller.com
Published: Feb 22 2008 / 09:35
The high complexity in our Java open source environment changes easy things to do, like migrating from java 1.5 to java 1.6, to a complex issue. These complexities need tools for collaborating in teams and in the Java community as a whole.
SaveShareSend
Tags: java, methodology, unix-linux, windows
-
Adding support for @PostConstruct, @PreDestroy and @Resource to Guice
-
Ignorance is the mother of invention
-
Cool opensource projects associated with Apache Shindig
-
IBM Websphere - officially better than anything, ever
-
Are You Missing The Point Of Being A Freelancer?
-
Why Must Internet Explorer Torture Me?
Comments
jtheory replied ago:
I'm curious to know some of the problems people see when upgrading -- I've needed to put a decent amount of work into continuing support of *old* JVMs, but normally I can slap in whatever JARs I find into any project with whatever current JVM, no matter how old they are, and they'll work with no problems.
The JREs are still largely backwards-compatible even to 1.0.2 code -- I imagine there are some exceptions, but I haven't hit them personally.
utakapp replied ago:
There seem to occur problems if you instantiate a class dynamically by a factory when the factory is compiled with java 1.5 while the instantiated class is compiled with java 1.6.
Voters For This Link (7)
Voters Against This Link (1)