On Fri, May 21, 2010 at 6:08 PM, Raymond Feng <[email protected]> wrote: > +1 to drop JDK 1.5 support. > The main benefit is that we will deal with much less dependencies, > especially for the core features. We can run some simple apps with just JDK > and Tuscany. > We can add the JDK 6 requirements into the maven-enforcer-plugin. > Thanks, > Raymond > ________________________________________________________________ > Raymond Feng > [email protected] > Apache Tuscany PMC member and committer: tuscany.apache.org > Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com > Personal Web Site: www.enjoyjava.com > ________________________________________________________________ > On May 21, 2010, at 7:54 AM, ant elder wrote: > > On Fri, May 21, 2010 at 3:48 PM, Simon Nash <[email protected]> wrote: > > ant elder wrote: > > On Wed, May 12, 2010 at 10:30 PM, Luciano Resende <[email protected]> > > wrote: > > The BUILDING file at trunk currently mention we require J2SE 5.0 SDK > > [1], but my understanding is that out current code only builds with > > J2SE 6.0 SDK. > > What should we do here ? Update that to JDK 6.0 ? > > > What is it that requires JDK6? Unless there is a real need for JDK6 > > then it would be nice to also keep support for JDK5 too. > > ...ant > > > There's a fair bit of extra work in keeping JDK 5 support going. I've been > > through this recently for the travel sample, and here's a summary of what > > I ran into: > > Need extra maven dependencies in various modules to pull in JAX-WS and JAXB > > Need to ship selected JAX-WS and JAXB jars in the Tuscany binary distro > > Need to compile all Java code with -source 1.5 and -target 1.5 > > Because of the above, need to run wsimport with -Xnocompile and run > > a separate compile step for the generated Java code > > Quadruples the testing work because of the need to test all of these: > > Build on Java 6, run on Java 6 > > Build on Java 5, run on Java 5 > > Build on Java 6, run on Java 5 > > Build on Java 5, run on Java 6 > > Java 6 has been around for over 3 years and is available (I think) on > > all major platforms. If anyone still needs Tuscany on Java 5, they > > can use Tuscany 1.x. I'd be inclined to drop Java 5 support from 2.x > > unless anyone has a compelling reason to keep it. > > Simon > > > > I think i agree with Simon now. We could set up all these tests and > have the Hudson build run with JDK5 to police it, but i tried the > other day and i know the 2.x build isn't working with JDK5 and there's > various funnies with generics causing compile errors and I'm not that > motivated to spend time on all this so unless someone else really is > then perhaps it is time to drop 1.5 support on 2.x. > > ...ant > >
+1 to go with just JDK6 Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
