HEADS UP: Switched to 1.8 source/target in build (in graphics repository).
tom.schindl at bestsolution.at
Tue May 7 11:56:19 PDT 2013
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
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.
More information about the openjfx-dev