by anjanb2 - 2005-04-06 13:28
by loke - 2005-04-06 05:54
Our app makes heavy use of annotations, which in my mind is the best new feature in 1.5. We've also adopted our code base for generics, although that is a feature which is much less useful than annotations.
The only 1.5 feature which is expressively banned in our project is static import. The recommendation is also that autoboxing is to be avoided.
by jwenting - 2005-04-04 00:22
by smartinumcp - 2005-03-31 07:45
by dog - 2005-03-28 12:28
Many dev organizations change environments only on the beginning stages of a major release. This can take 6 months to a year once the new technology is percieved to be "ready".
We'll be moving to 1.5 on a new product, but I don't know how many of the new cool features we'll use since we still need backwards compatibility. So many we'll complie for 1.4 compliance but run on 1.5. Our main reason to move to 1.5 is performance issues.
On existing products we've only just moved to 1.4.
by rickcarson - 2005-03-27 16:50
by cajo - 2005-03-25 14:51
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Participation.
Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.