Carlos, suppose it turns out that we can't be compatible with both 6 and 7. (I hope that's not the case, but I don't think we know yet.) Are you saying we have to stick with 6? Rather than do that, we should probably instead have two branches and two builds if we can't have compatibility with both.
- Gordon -----Original Message----- From: carlos.rov...@gmail.com [mailto:carlos.rov...@gmail.com] On Behalf Of Carlos Rovira Sent: Tuesday, January 21, 2014 2:03 PM To: dev@flex.apache.org Subject: Re: Java 1.6 I'd like to go Java 7, but in my case we have products in Java 6 that can't be upgraded right now. I suppose that many people are in the same situation. So I think compatibility with Java 6 is a must. 2014/1/21 Gordon Smith <gosm...@adobe.com> > 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 > > -- Carlos Rovira Director de Tecnología M: +34 607 22 60 05 F: +34 912 94 80 80 http://www.codeoscopic.com http://www.directwriter.es http://www.avant2.es
