I am in favor of project requirements somewhat driving organizations to upgrade. I was even hoping initially that we might start out with JDK7 as a minimum. True that no compelling features require the use of JDK7 (That I know of, there may be some!) but with JDK6 EOL around the corner, maybe the next CAS release would specify the requirement for a platform still in support going forward.
One example that comes to mind is, the new watch service and notifications API in JDK7 would have come in handy for building a version of the service registry that is externalized to a file and reloaded on change. (Though Spring offers similar support in the area and does the job quite well) P.S: we also may want to think about the Tomcat and Maven requirements. I think we are set at Tomcat5 and Maven2, as the docs currently suggest. Regards, -Misagh From: Scott Battaglia [mailto:[email protected]] Sent: Wednesday, August 01, 2012 11:43 AM To: [email protected] Subject: Re: [cas-dev] Next CAS release + JDK 6 If we're looking to use our position as away to push people to upgrade their EOL-ed stuff, than I am for making Java 6 the minimum (i.e. some organizations won't upgrade until something forces them too). I typically look at it from the perspective of what is in 1.6 (or 1.7) that is helpful enough to us at the development team to enforce some minimum on the deployers. I didn't see anything compelling enough in a 1.6 API for us that made it worth it to force a higher minimum. Cheers, Scott On Wed, Aug 1, 2012 at 2:07 PM, Dmitriy Kopylenko <[email protected]> wrote: Yes, so? :-) Java 5 is EOL for a long time and Java 6 EOL is here. So, I personally see no reason to support "ancient" versions. Cheers, D. On Wed, Aug 1, 2012 at 1:54 PM, Scott Battaglia <[email protected]> wrote: Isn't that what this thread is supposed to be discussing? On Wed, Aug 1, 2012 at 1:47 PM, Dmitriy Kopylenko <[email protected]> wrote: The Wiki is updated stating that minimum JDK for CAS 4.x will be 1.6: https://wiki.jasig.org/display/CASUM/Java+Versions On Wed, Aug 1, 2012 at 1:42 PM, Scott Battaglia <[email protected]> wrote: If it doesn't say 1.5 or higher, than it should be corrected. Its intended to say 1.5 or higher. On Wed, Aug 1, 2012 at 1:33 PM, Misagh Moayyed <[email protected]> wrote: Not aware of any specific language features devs might need, but given the major coming release I think it's a good time to up the version requirement and anticipate the need, so to speak. Perhaps the word "requirement" is not the best phrasing. What I have in mind mostly falls down to the level of "Does CAS run or support JDK6 and above?" The official wording that CAS requires 1.5 sort of gives the impression that if folks proceed with a later java version, the upgrade will break something in CAS. -Misagh From: Scott Battaglia [mailto:[email protected]] Sent: Monday, July 30, 2012 2:39 PM To: [email protected] Subject: Re: [cas-dev] Next CAS release + JDK 6 Is there a compelling feature that would make us want to require 1.6? On Jul 30, 2012 5:09 PM, "Misagh Moayyed" <[email protected]> wrote: Team, Given the next major CAS release in planning, I wanted to propose that we up the JDK requirement for CAS from the 5 to 6. As far as I know, there aren't any particular changes in the codebase that depend on JDK5 specifically and we at Unicon have been doing CAS deployments based on the JDK6 platform with much success. (I could possibly safely assume that most other adopters are already on JDK6, if not later). I think switching the platform requirement to 6 at the time of a major release would be a reasonable. Feedback is welcome :) Regards, -Misagh -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
