I agree with most of it, except that some part needs to be carefully designed when migrated to generics. I started to read about it, and generics are not trivial to introduce in a framework when that framework manipulates reflection code. So those parts should be done carefully. Any non trivial migration to Java 5 syntax should be discussed and reviewed before. "bdaw" wrote : Actually I don't see the big problem here: | - we don't need to upgrade whole codebase to the java 5 syntax (time consuming + branch sync issues) | - when you bug fix you code with backport (svn merge) in mind so probably won't use new syntax anywa... | - when you add new features you change/refactor a lot so such part can't be backported easily, and probably isn't supposed to be backported at all.... | | So lets naturally use java 5 in trunk for new stuff and during refactorings, and don't upgrade old code "just to". | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4061265#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...