[prev in list] [next in list] [prev in thread] [next in thread]
List: openjdk-openjfx-dev
Subject: Re: Will OpenJFX have a release ready in time for the Java 11 launch?
From: Paul Ray Russell <paulrussell70 () gmail ! com>
Date: 2018-04-06 7:28:35
Message-ID: CA+oj-NvQSKpiU4hoKB5Y5sbiSPge5WtgJxLxyQJiP9rxDmF-zQ () mail ! gmail ! com
[Download RAW message or body]
+1 :)
"This is imo the most important work right now, and a number of people are
working on it.
I am very positive this [both paths] will be realised before the Java 11
release date. "
On 6 April 2018 at 01:21, <openjfx-dev-request@openjdk.java.net> wrote:
> Send openjfx-dev mailing list submissions to
> openjfx-dev@openjdk.java.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mail.openjdk.java.net/mailman/listinfo/openjfx-dev
> or, via email, send a message with subject or body 'help' to
> openjfx-dev-request@openjdk.java.net
>
> You can reach the person managing the list at
> openjfx-dev-owner@openjdk.java.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of openjfx-dev digest..."
>
>
> Today's Topics:
>
> 1. Re: gradle :web:test fails (Kevin Rushforth)
> 2. Will OpenJFX have a release ready in time for the Java 11
> launch? (Mikael Christensen - QIAGEN)
> 3. Re: Will OpenJFX have a release ready in time for the Java 11
> launch? (Kevin Rushforth)
> 4. Re: Will OpenJFX have a release ready in time for the Java 11
> launch? (Johan Vos)
> 5. Re: gradle :web:test fails (Nir Lisker)
> 6. Re: HEADS-UP: Proposal to bump the minimum boot JDK for FX to
> JDK 10 (Kevin Rushforth)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 05 Apr 2018 05:01:13 -0700
> From: Kevin Rushforth <kevin.rushforth@oracle.com>
> To: Murali Billa <murali.billa@oracle.com>
> Cc: "openjfx-dev@openjdk.java.net Mailing"
> <openjfx-dev@openjdk.java.net>
> Subject: Re: gradle :web:test fails
> Message-ID: <5AC61009.9080104@oracle.com>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> Yes, this is very likely the issue. If you take the jfxwebkit.dll from
> the latest EA build of JDK 11 then you should be fine. Alternatively, if
> you have the patience to build webkit from source (at least once) then
> you can use that.
>
> Johan had a good idea that gradle :web:test should produce a warning if
> COMPILE_WEBKIT is false [1].
>
> I just now filed a bug [2] to track this.
>
> -- Kevin
>
> [1]
> https://github.com/javafxports/openjdk-jfx/issues/19#issuecomment-
> 378521501
> [2] https://bugs.openjdk.java.net/browse/JDK-8201176
>
>
> Murali Billa wrote:
> > Hi Lisker,
> >
> > +one more point:
> >
> > I think you are not compiling webkit . The command "gradle :web:test"
> picks the webkit dll from JDK (which can have older versions like 10 / 9) .
> >
> > You can compile webkit with command " gradle -PCOMPILE_WEBKIT=true
> :web:test" and in this case webkit dll will be picked up from your source
> code repo (not from JDK).
> >
> > Thanks,
> > Murali
> >
> > -----Original Message-----
> > From: Murali Billa
> > Sent: Thursday, April 05, 2018 10:19 AM
> > To: Nir Lisker <nlisker@gmail.com>; openjfx-dev@openjdk.java.net
> Mailing <openjfx-dev@openjdk.java.net>
> > Subject: RE: gradle :web:test fails
> >
> > Hi Lisker,
> >
> > Can you print the value of useragentString ? Looks like you are using
> fxversion as 11 (you can print this value from System.getProperty("javafx.runtime.version");)
> but the useragentstring does not contain 11.
> >
> > final WebView webView = new WebView();
> > final WebEngine webEngine = webView.getEngine();
> System.out.println(webEngine.getUserAgent());
> >
> >
> > Thanks,
> > Murali
> > -----Original Message-----
> > From: Nir Lisker <nlisker@gmail.com>
> > Sent: Thursday, April 05, 2018 7:03 AM
> > To: openjfx-dev@openjdk.java.net Mailing <openjfx-dev@openjdk.java.net>
> > Subject: gradle :web:test fails
> >
> > I'm running :web:test in revision 10889 and getting the following failing
> > test:
> >
> > test.javafx.scene.web.MiscellaneousTest > testUserAgentString FAILED
> > java.lang.AssertionError: UserAgentString does not contain JavaFX/11
> > at org.junit.Assert.fail(Assert.java:91)
> > at org.junit.Assert.assertTrue(Assert.java:43)
> > at
> > test.javafx.scene.web.MiscellaneousTest.lambda$testUserAgentString$12(
> MiscellaneousTest.java:441)
> >
> > 379 tests completed, 1 failed, 12 skipped :web:test FAILED
> >
> > Is this known?
> >
> > - Nir
> >
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 5 Apr 2018 12:12:32 +0000
> From: Mikael Christensen - QIAGEN <Mikael.Christensen@qiagen.com>
> To: "openjfx-dev@openjdk.java.net" <openjfx-dev@openjdk.java.net>
> Subject: Will OpenJFX have a release ready in time for the Java 11
> launch?
> Message-ID:
> <HE1PR05MB1675F1A89E46E2614CB53A16EDBB0@HE1PR05MB1675.
> eurprd05.prod.outlook.com>
>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi,
>
> This is a question about Oracle's statement that JavaFX will no longer be
> part of the SDK starting from Java 11:
> https://blogs.oracle.com/java-platform-group/the-future-of-
> javafx-and-other-java-client-roadmap-updates
>
> Is the plan, that when Java 11 is released (scheduled for September 2018),
> it will be possible to download a (prebuilt) JavaFX component from the
> OpenJFX?
>
> Best, Mikael.
>
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 05 Apr 2018 05:21:46 -0700
> From: Kevin Rushforth <kevin.rushforth@oracle.com>
> To: Mikael Christensen - QIAGEN <Mikael.Christensen@qiagen.com>
> Cc: "openjfx-dev@openjdk.java.net" <openjfx-dev@openjdk.java.net>
> Subject: Re: Will OpenJFX have a release ready in time for the Java 11
> launch?
> Message-ID: <5AC614DA.1090803@oracle.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Yes, this is the plan. There has been quite a lot of discussion on this,
> so I invite you to search the email archives [1]. Specifically, the
> recent "modules versus SDK's" thread [2]. You are welcome to join the
> mailing list [3] and contribute to the discussion if you like.
>
> -- Kevin
>
> [1] http://mail.openjdk.java.net/pipermail/openjfx-dev/
> [2]
> http://mail.openjdk.java.net/pipermail/openjfx-dev/2018-March/021624.html
> [3] http://mail.openjdk.java.net/mailman/listinfo/openjfx-dev
>
>
> Mikael Christensen - QIAGEN wrote:
> > Hi,
> >
> > This is a question about Oracle's statement that JavaFX will no longer
> be part of the SDK starting from Java 11:
> > https://blogs.oracle.com/java-platform-group/the-future-of-
> javafx-and-other-java-client-roadmap-updates
> >
> > Is the plan, that when Java 11 is released (scheduled for September
> 2018), it will be possible to download a (prebuilt) JavaFX component from
> the OpenJFX?
> >
> > Best, Mikael.
> >
> >
>
>
> ------------------------------
>
> Message: 4
> Date: Thu, 05 Apr 2018 12:29:54 +0000
> From: Johan Vos <johan.vos@gluonhq.com>
> To: Mikael Christensen - QIAGEN <Mikael.Christensen@qiagen.com>
> Cc: "openjfx-dev@openjdk.java.net" <openjfx-dev@openjdk.java.net>
> Subject: Re: Will OpenJFX have a release ready in time for the Java 11
> launch?
> Message-ID:
> <CABxFH2HUHfv3MjR8hSra=xG25g1p27mPWTy07JDe9M9KR==xSw@
> mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Yes, that is the plan.
>
> Actually, there are 2 paths:
> 1. create a JavaFX SDK (see https://bugs.openjdk.java.net/
> browse/JDK-8198329
> )
> 2. create and upload the JavaFX modules to the traditional, popular
> repositories (maven central, bintray) and make sure developers can use the
> API's using maven/gradle (see
> https://github.com/javafxports/openjdk-jfx/issues/52)
>
> This is imo the most important work right now, and a number of people are
> working on it.
>
> I am very positive this [both paths] will be realised before the Java 11
> release date.
>
> - Johan
>
> On Thu, Apr 5, 2018 at 2:25 PM Mikael Christensen - QIAGEN <
> Mikael.Christensen@qiagen.com> wrote:
>
> > Hi,
> >
> > This is a question about Oracle's statement that JavaFX will no longer be
> > part of the SDK starting from Java 11:
> >
> > https://blogs.oracle.com/java-platform-group/the-future-of-
> javafx-and-other-java-client-roadmap-updates
> >
> > Is the plan, that when Java 11 is released (scheduled for September
> 2018),
> > it will be possible to download a (prebuilt) JavaFX component from the
> > OpenJFX?
> >
> > Best, Mikael.
> >
> >
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 6 Apr 2018 02:14:14 +0300
> From: Nir Lisker <nlisker@gmail.com>
> To: Kevin Rushforth <kevin.rushforth@oracle.com>
> Cc: "openjfx-dev@openjdk.java.net Mailing"
> <openjfx-dev@openjdk.java.net>
> Subject: Re: gradle :web:test fails
> Message-ID:
> <CA+0ynh_zOYU8D9PjrZa98qmJOkPDEpNGz61g+
> -mtyF9YAYezYg@mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Yes, I didn't build Webkit and the JDK is 10, but I thought the Webkit
> tests would be skipped if it weren't built.
>
> The filed bug should do it. Thanks.
>
> - Nir
>
> On Thu, Apr 5, 2018, 15:01 Kevin Rushforth <kevin.rushforth@oracle.com>
> wrote:
>
> > Yes, this is very likely the issue. If you take the jfxwebkit.dll from
> > the latest EA build of JDK 11 then you should be fine. Alternatively, if
> > you have the patience to build webkit from source (at least once) then
> > you can use that.
> >
> > Johan had a good idea that gradle :web:test should produce a warning if
> > COMPILE_WEBKIT is false [1].
> >
> > I just now filed a bug [2] to track this.
> >
> > -- Kevin
> >
> > [1]
> > https://github.com/javafxports/openjdk-jfx/issues/19#issuecomment-
> > 378521501
> > [2] https://bugs.openjdk.java.net/browse/JDK-8201176
> >
> >
> > Murali Billa wrote:
> > > Hi Lisker,
> > >
> > > +one more point:
> > >
> > > I think you are not compiling webkit . The command "gradle :web:test"
> > picks the webkit dll from JDK (which can have older versions like 10 /
> 9) .
> > >
> > > You can compile webkit with command " gradle -PCOMPILE_WEBKIT=true
> > :web:test" and in this case webkit dll will be picked up from your source
> > code repo (not from JDK).
> > >
> > > Thanks,
> > > Murali
> > >
> > > -----Original Message-----
> > > From: Murali Billa
> > > Sent: Thursday, April 05, 2018 10:19 AM
> > > To: Nir Lisker <nlisker@gmail.com>; openjfx-dev@openjdk.java.net
> > Mailing <openjfx-dev@openjdk.java.net>
> > > Subject: RE: gradle :web:test fails
> > >
> > > Hi Lisker,
> > >
> > > Can you print the value of useragentString ? Looks like you are using
> > fxversion as 11 (you can print this value from
> System.getProperty("javafx.runtime.version");)
> > but the useragentstring does not contain 11.
> > >
> > > final WebView webView = new WebView();
> > > final WebEngine webEngine = webView.getEngine();
> > System.out.println(webEngine.getUserAgent());
> > >
> > >
> > > Thanks,
> > > Murali
> > > -----Original Message-----
> > > From: Nir Lisker <nlisker@gmail.com>
> > > Sent: Thursday, April 05, 2018 7:03 AM
> > > To: openjfx-dev@openjdk.java.net Mailing <openjfx-dev@openjdk.java.net
> >
> > > Subject: gradle :web:test fails
> > >
> > > I'm running :web:test in revision 10889 and getting the following
> failing
> > > test:
> > >
> > > test.javafx.scene.web.MiscellaneousTest > testUserAgentString FAILED
> > > java.lang.AssertionError: UserAgentString does not contain
> JavaFX/11
> > > at org.junit.Assert.fail(Assert.java:91)
> > > at org.junit.Assert.assertTrue(Assert.java:43)
> > > at
> > > test.javafx.scene.web.MiscellaneousTest.lambda$testUserAgentString$12(
> > MiscellaneousTest.java:441)
> > >
> > > 379 tests completed, 1 failed, 12 skipped :web:test FAILED
> > >
> > > Is this known?
> > >
> > > - Nir
> > >
> >
>
>
> ------------------------------
>
> Message: 6
> Date: Thu, 05 Apr 2018 17:21:02 -0700
> From: Kevin Rushforth <kevin.rushforth@oracle.com>
> To: "openjfx-dev@openjdk.java.net" <openjfx-dev@openjdk.java.net>
> Subject: Re: HEADS-UP: Proposal to bump the minimum boot JDK for FX to
> JDK 10
> Message-ID: <5AC6BD6E.5090302@oracle.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> I created a pull request [3] for this, and discovered that the CI builds
> for the GitHub sandbox are using JDK 9.0.4. Michael Ennen is fixing this
> by switching both the Travis and Appveyor CI builds to use JDK 10 [4].
>
> Given the disruptive nature of bumping the minimum, I think it is wise
> to wait another day or two before taking any action on my proposal to
> bump the minimum (we can and should still proceed to upgrade the CI
> builds to use JDK 10). This will give others who might have concerns a
> chance to comment.
>
> Comments?
>
> -- Kevin
>
> [3] https://github.com/javafxports/openjdk-jfx/pull/61
>
> [4] https://github.com/javafxports/openjdk-jfx/pull/63
>
>
> Kevin Rushforth wrote:
> > As mentioned in another thread [1] we should update the minimum boot
> > JDK used to build FX to 10, which will allow the use of JDK 10
> > langauge features, such as 'var', as well as JDK 10 APIs. It's also
> > the right time to do this in general. I filed a new RFE [2] to track
> > this and plan to send it out for review next week.
> >
> > Please let me know if there are any concerns. We already use JDK 10 to
> > build FX 11 ea bits. I presume that the travis and appveyor CI builds
> > of the github mirror do the same?
> >
> > -- Kevin
> >
> > [1]
> > http://mail.openjdk.java.net/pipermail/openjfx-dev/2018-
> March/021671.html
> >
> > [2] https://bugs.openjdk.java.net/browse/JDK-8200446
> >
>
>
> End of openjfx-dev Digest, Vol 77, Issue 9
> ******************************************
>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic