I am actually a reluctant +0 on this. I won't hold it up if everyone votes for it, but I am still not convinced its the right decision.

So far I am yet to hear a real reason why we should or better yet why we *need* to switch to 1.5. While its true that this probably won't affect most people, we are still going to be alienating at least some portion of our userbase who for some reason or another is running on 1.4. It doesn't seem very community/customer friendly to do that.

My personal feeling is that it's somewhat irresponsible to upgrade the jdk just because we want to and not because we really need to.

SIDE NOTE: one thing that did come up in the mini-hackathon on wednesday was the problem of JPA requiring 1.5. Mitesh was going to double check on it, but it sounds like that's the case. If so then this would be an actual reason to go to 1.5, if we decide we want to support a JPA backend.

-- Allen


Anil Gangolli wrote:

+1.

with several comments:

- I've been using 1.5 at runtime for Roller in Tomcat 5.5.x for some time.

- There is a longtime complaint (ROL-644) from one user that 1.5 breaks Roller and Velocity 1.4, except on Tomcat 5.5, and that we would need to remove a bunch of leading slashes from velocity resource paths to make it work on other app servers. This bears some looking into if we switch, or perhaps we upgrade to Velocity 1.5, which also reportedly resolves this.

- While initially this would be just a flip of a switch, it would be good to write down what this means for our coding conventions, particularly around the use of generics in declarations and our casting conventions for dealing with the libs and any other code returning "plain" collections.

- We'll see people start using autoboxing (inadvertently even :-); and we can expect a few mysterious NPEs cropping up.

--a.


----- Original Message ----- From: "Matt Raible" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, September 15, 2006 7:50 AM
Subject: Re: Java 5?


+1 for now!  I'm doing it in AppFuse.  You could always use
Retroweaver for folks wanting to deploy to 1.4.  The only reason I can
think of wanting to deploy to 1.4 is because they're using some
WebSphere 5.1 or something.

Matt

On 9/15/06, Dave Johnson <[EMAIL PROTECTED]> wrote:
When can we switch over to Java 5? I'm getting tired of juggling JVMs
and living in the past.

- Dave



Reply via email to