+1 I did a quick test on Mac and it worked for me.
Chris
> On Nov 8, 2016, at 4:11 PM, Kevin Rushforth
> wrote:
>
> Hi,
>
> Please review the following fix to include jake-compatible versions of
> module-info.java with our input bundles:
>
>
Looks good to me.
Mandy
> On Nov 8, 2016, at 4:11 PM, Kevin Rushforth
> wrote:
>
> Hi,
>
> Please review the following fix to include jake-compatible versions of
> module-info.java with our input bundles:
>
> https://bugs.openjdk.java.net/browse/JDK-8169417
>
There are times when you just have to break the rules :-)
And when it comes to module package internals visibility, we have to at least
bend the rules a bit, particularly for testing.
In comes the 'addExports" file. These files in the FX tree are actually
'argfiles' passed to javac
What do you need to know about the new modular build (or how does this affect
me ?)
I have covered the need for a new Gradle 3.1+, JDK 9 build 142+ already, so
moving beyond that
FIVE Shocking things you need to know about the new build !!! :-)
FIRST:
There is NO jfxrt.jar
The new modular build has been committed to 9-dev !!!
To ensure a continued happy development, please consider the following advice
:-)
Clean up your old repository before syncing.
gradle clean
consider (but not required)
hg purge --all
unset JIGSAW_HOME # this enviroment variable is
Hi,
I think we should wait for OpenJFX9 Jigsaw build patch that is coming and
rebase / test again the proposed patch Marlin for JavaFX.
Maybe jdk.internal.Cleaner or Unsafe.allocateDirect methods will be then
available to the javafx.graphics module or that may be acceptable to export
such jdk
Hi John,
In regard to your input issue. If it's a possibility, I'd recommend looking
at 'libinput'. It's an generic input abstraction library. It might be more
up to date and provide quirk fixes for (all kind of) input hardware.
https://wayland.freedesktop.org/libinput/doc/latest/
It's already