HEADS UP: Switched to 1.8 source/target in build (in graphics repository).

[Tom Schindl]

The problem is that the compiler eg does not create bytecode for lambdas but simply puts null into the .class file. Support for public defender methods is almost done!

Tom

Von meinem iPhone gesendet

Am 07.05.2013 um 21:57 schrieb Felipe Heidrich <felipe.heidrich at oracle.com>:

> 
> I have 4.3M7 installed I see no support for Java 8. I think Tom has it right.
> 
> See
> http://wiki.eclipse.org/JDT_Core/Java8
> http://wiki.eclipse.org/JDT_UI/Java8
> 
> I downloaded 
> git clone -b  BETA_JAVA8 ssh://fheidric@git.eclipse.org/gitroot/jdt/eclipse.jdt.ui.git
> git clone -b  BETA_JAVA8 ssh://fheidric@git.eclipse.org/gitroot/jdt/eclipse.jdt.core.git
> 
> Imported it all to 4.3M7 and self-hosted, now I can see compiler compliance level of 1.8 Beta in the preference page.
> I'm still working to make it work for JFX…
> 
> Felipe
> 
> 
> 
> On May 7, 2013, at 11:56 AM, Tom Schindl wrote:
> 
>> I highly doubt that eclipse can handle *any* java8 code you'd have to run with a special jdt git branch. You can see the state in http://wiki.eclipse.org/JDT_Core/Java8 and/or https://bugs.eclipse.org/bugs/show_bug.cgi?id=380190
>> 
>> Tom
>> 
>> Von meinem iPhone gesendet
>> 
>> Am 07.05.2013 um 20:48 schrieb Jonathan Giles <jonathan.giles at oracle.com>:
>> 
>>> I did have trouble with eclipse once we moved to Java 8 earlier in the week, but this was really fixed by updating my eclipse install to instead be the latest Kepler (4.3) milestone build, rather than 4.2.2.
>>> 
>>> 
>>> -- Jonathan
>>> Sent from a touch device. Please excuse my brevity.
>>> 
>>> Richard Bair <richard.bair at oracle.com> wrote:
>>>> 
>>>>> People using Eclipse as their IDE will not have fun with that I guess because their IDE will not compile the code anymore, so one can't use Eclipse anymore to provide patches - nothing you really care I guess.
>>>> 
>>>> Steve, Felipe, or Jonathan would have to comment on what this does to them I guess -- they all use Eclipse for development.
>>>> 
>>>>> I don't argue that you should not do this because Eclipse does not yet support it (which is a shame for Eclipse) but you are excluding other VMs who don't support those concepts - most notable invoke dynamic - this makes a community port of JavaFX to iOS fairly impossible.
>>>> 
>>>> I think it would be fairly easy to just filter out those classes and replace the ObservableList with a version that doesn't have the defender methods. We had to do such things to make JavaFX mobile work back in the day. It is a short term problem because VMs and IDEs are going to move forward.
>>>> 
>>>> Richard
>