HEADS UP: Switched to 1.8 source/target in build (in graphics repository).
richard.bair at oracle.com
Tue May 14 07:40:16 PDT 2013
We will make this as easy for you as we can by not using JDK 8 only functionality all over the place.
On May 13, 2013, at 8:33 AM, Danno Ferrin <danno.ferrin at shemnon.com> wrote:
> On Mon, May 13, 2013 at 9:17 AM, Tom Schindl <tom.schindl at bestsolution.at>wrote:
>> Hi Steve,
>> In the case of Eclipse, I have built the JDK8 Beta JDT plugins and am
>>> self hosting with them. I am in the process of evaluating whether they
>>> will be sufficient. It is also possible to run Eclipse using the patch
>>> and put both JDK7 and JDK8 on the build path (JDK7 first). This will
>>> allow you to see JDK7 classes first to avoid changes to the base
>>> libraries. At runtime, you should run against JDK8. Neither of these
>>> solutions is great so we will have to wait and see.
>> Ok - keep me updated on this. IIRC the lambda stuff currently does NOT
>> produce any bytecode (last time i checked it simply wrote null intead of
>> the invoke dynamic).
>> If this has changed in the meantime this is good news. So report back your
>> findings I could make a JDT_Beta download available from efxclipse.org.
>> It might make sense to host them in an extra branch instead of a JIRA,
>> not? I think we should setup a bitbucket repo where we attach this (and
>> patches who will follow) keep stuff compiling on JDK7 (see current
>> RoboVM-Thread which does NOT support invoke dynamic).
>> Danno could we do it in your repo?
> This is precisely why I set up the Narya repo on bitbucket. However I
> won't be able to do much until I get off of work today
> Right now I see at least two repos we may want to start:
> 1) JDK7 version of JavaFX8. Consisting of stripping lambdas into inner
> classes as well as other changes needed such as bringing in a JSR310
> standalone jar for date picker and providing alternative APIs for defender
> methods interfaces.
> 2) a mirror of the RoboVM samples when they are released/
More information about the openjfx-dev