Re: RE : RE : Java 1.6

2014-01-23 Thread Tom Chiverton
On 22/01/2014 17:12, Alex Harui wrote: On 1/22/14 7:49 AM, "Erik de Bruin" wrote: At least as the default. No harm in also offering legacy version(s). But more work if you are suggesting that the release manager has to produce convenience binaries in both Java 6 and Java 7. The installer pro

Re: RE : RE : Java 1.6

2014-01-22 Thread Alex Harui
On 1/22/14 7:49 AM, "Erik de Bruin" wrote: >At least as the default. No harm in also offering legacy version(s). But more work if you are suggesting that the release manager has to produce convenience binaries in both Java 6 and Java 7. The installer probably also has to change, and it is anot

Re: RE : RE : Java 1.6

2014-01-22 Thread Erik de Bruin
At least as the default. No harm in also offering legacy version(s). EdB On Wed, Jan 22, 2014 at 4:47 PM, Tom Chiverton wrote: > We should be setting an example and moving to something that isn't full of > holes :-) > > Tom > > > On 22/01/2014 15:37, Alex Harui wrote: >> >> I'm ok with that, b

Re: RE : RE : Java 1.6

2014-01-22 Thread Tom Chiverton
We should be setting an example and moving to something that isn't full of holes :-) Tom On 22/01/2014 15:37, Alex Harui wrote: I'm ok with that, but an alternate plan is just to have Jenkins run Java 6.

Re: RE : RE : Java 1.6

2014-01-22 Thread Alex Harui
On 1/22/14 3:44 AM, "Tom Chiverton" wrote: >On 22/01/2014 09:52, Erik de Bruin wrote: >> IF we need two separate builds for the binaries, I can set it up. >> Either on thebuilds@a.o machine >I think that would be best. Then at least we'll know if we broke >something :-) I'm ok with that, but a

Re: RE : RE : Java 1.6

2014-01-22 Thread Tom Chiverton
On 22/01/2014 09:52, Erik de Bruin wrote: IF we need two separate builds for the binaries, I can set it up. Either on thebuilds@a.o machine I think that would be best. Then at least we'll know if we broke something :-) Tom

RE: RE : Java 1.6

2014-01-22 Thread Kessler CTR Mark J
One side note. You should be able to have different versions of Java installed. -Mark

Re: RE : RE : Java 1.6

2014-01-22 Thread Erik de Bruin
. Januar 2014 00:17 > An: dev@flex.apache.org > Betreff: RE : RE : Java 1.6 > > Im still not clear with the impact of the built sdk on application and I > maybe mis understood for FM but thought it was ok to use it but not to built > it only. > > Thanks. > > >

AW: RE : RE : Java 1.6

2014-01-21 Thread Christofer Dutz
endet: Mittwoch, 22. Januar 2014 00:17 An: dev@flex.apache.org Betreff: RE : RE : Java 1.6 Im still not clear with the impact of the built sdk on application and I maybe mis understood for FM but thought it was ok to use it but not to built it only. Thanks. Envoyé depuis un mobile Sa

RE : RE : Java 1.6

2014-01-21 Thread webdoublefx
00:00) A : dev@flex.apache.org Objet : Re: RE : Java 1.6 Right, people using flexmojos, java on server side and so on with Java 6 will have to migrate all to get all the system in the same version of Java. But it implies changes to flexmojos to get working with Java 7 (as Chris said). Maybe people

Re: RE : Java 1.6

2014-01-21 Thread Carlos Rovira
Right, people using flexmojos, java on server side and so on with Java 6 will have to migrate all to get all the system in the same version of Java. But it implies changes to flexmojos to get working with Java 7 (as Chris said). Maybe people could opt for a gradual migration and start only with fle