Well, I'll tryŠ But there remains a logistical issue, even if this is possible which is: Currently the Jenkins builds that create the Nightly Builds are using Java 7 to build the compilers, and then you can't download and use the compilers on Java 6.
This is fine from a pure Apache perspective since we only officially release source code and then folks choose Java 6 or 7 to build their own compilers, but from a practical perspective, many more folks just grab the binaries. Should we continue to compile and release our convenience binaries on Java 6? -Alex On 1/21/14 12:56 PM, "Gordon Smith" <gosm...@adobe.com> wrote: >We should definitely fix the problems that make us incompatible with Java >7, and then make that our recommended version (and switch out build >systems). But staying compatible with Java 6, if that's possible, would >also be a good thing. > >- Gordon > >-----Original Message----- >From: aYo [mailto:a...@binitie.com] >Sent: Tuesday, January 21, 2014 11:41 AM >To: dev@flex.apache.org >Subject: Re: Java 1.6 > >The future is Java 7+, but I think we need to be 6 compatible for a >while. There will be lots of teams out there that will not be pleased if >there is a sudden loss of support for 6. As you know, it can be seriously >disruptive > >On Tue 21 Jan 2014 20:35:55 WAT, Alex Harui wrote: >> More and more things are requiring Java 7. Java 6 standard support is >> over. Should we just move to Java 7 or do we need to remain Java 6 >> compatible? BTW, there appears to be errors when you try to get Flex >> to build on Java 7. I'm looking into it now. >> >> Thoughts? >> -Alex >> > >-- >*aYo* >www.ayobinitie.com >mrbinitie.blogspot.com >
