I've adapted the build.gradle to use java -fullversion instead of java
-version, parsing the result with a regexp.
diff -r 9b5fc7c1e5e6 build.gradle
--- a/build.gradle Fri Aug 07 18:35:42 2015 -0700
+++ b/build.gradle Thu Aug 27 15:52:11 2015 +0200
@@ -719,29 +719,27 @@
if
It's not directly related to JEP 257, no. Just some outstanding cleanup.
Btw, speaking of JEP 257, we plan to integrate that to 9-dev today.
-- Kevin
Michael Berry wrote:
+1 for deprecation - I haven't used VP6 in a long while, and would value
the whole thing being open source more than its
+1 for deprecation - I haven't used VP6 in a long while, and would value
the whole thing being open source more than its inclusion.
Out of interest, is this anything to do with JEP 257? I started looking at
this with Kirill's guidance a year or so ago, but sadly many other things
had to
On 27 August 2015 at 19:53, David DeHaven david.deha...@oracle.com wrote:
+1 for deprecation - I haven't used VP6 in a long while, and would value
the whole thing being open source more than its inclusion.
Out of interest, is this anything to do with JEP 257? I started looking
at
this
Hi all,
As promised the other week here is an updated javadoc export of the
proposed APIs for JEP 253. It includes the APIs for the third subproject
(new CSS APIs), and it also _removes_ the APIs for the second subproject
(InputMap APIs).
The URL for the JavaDoc is here:
I just pushed the changeset for JEP 257 [1] [2] on behalf of Alexander
Matveev to the openjfx 9-dev repo. If you have any questions about the
new GStreamer, please let Alexander or Kirill know. This will be in next
week's early access build of JDK 9 (build 80).
As previously announced [3]
I hereby nominate Alexander Matveev [1] to OpenJFX Committer.
Alexander was an initial member of JavaFX team at Oracle when the
OpenJFX project was created, and was on the initial list of approved
committers [2]. His status as OpenJFX committer was not recorded at that
time on the Census.
Ok. That what I assumed.
Shall we try to compile a list with needed API's?
-Sven
Am 26.08.2015 19:19 schrieb Pedro Duque Vieira
pedro.duquevie...@gmail.com:
I've also extended charts and have also been confronted with internal APIs.
--
Pedro Duque Vieira
On 27.08.2015 9:29, Dr. Michael Paus wrote:
To me this sounds again like a Java/JavaFX specific solution which, to
my opinion, is a dead-end road. I think it would be much more important
that JavaFX can directly use all system installed codecs. I simply don't
understand why it is possible to
