Refactoring JavaFX Builds & Sources

[Daniel Zwolenski]

In terms of building the various assets, like jfx-ant-tools.jar (or whatever its called), winlauncher.exe, etc. 

Currently the ant scripts for doing this don't work out of the box and need fixing. The Oracle guys who have inherited them have/had as much issues as me trying to build on the various platforms. 

So just wondering if these gradle scripts make life any better in any way in this respect and also wondering about the consistency here: gradle for one, gradle for all, or every module for himself?



On 02/02/2013, at 8:50 AM, Richard Bair <richard.bair at oracle.com> wrote:

> In terms of where the code lives and such, or in terms of how the deployment tools work?
> 
> On Feb 1, 2013, at 1:49 PM, Daniel Zwolenski <zonski at gmail.com> wrote:
> 
>> Will this cover building the deployment/packaging libraries (currently a mess)?
>> 
>> 
>> 
>> On 02/02/2013, at 5:29 AM, Richard Bair <richard.bair at oracle.com> wrote:
>> 
>>> OK, I've split the generation script into two pieces -- one is closed and one is open. The open one contains all the logic for creating a "javafx" directory sibling of rt and copying sources etc into it, in the new directory layout.
>>> 
>>> It doesn't build yet unless jfxrt.jar is on the class path. If you manage to get the right version of the file it should build -- modulo the printing build break that is awaiting the next weekly build.
>>> 
>>> Richard
>