For the apps (e.g., Ensemble8), we use call ant from gradle to build
anyway, so pointing NB at them seems best.
For the runtime itself, we tried using an earlier version of the
NetBeans Gradle plugin, but were not successful, so we ended up
producing netbeans files that are used only by the IDE. If a newer
version of the NB gradle plugin works well enough, then it would be
great if we could retire these files.
Stephen F Northover wrote:
We are not currently using the gradle plugins for any of the IDE's.
On 2014-02-14 7:26 PM, Scott Palmer wrote:
Are you guys using the NetBeans Gradle plugin?
On Fri, Feb 14, 2014 at 2:17 PM, Kevin Rushforth
For NB 7.4 (or 8) users, you should be able to just open up the apps
projects in NB and have it work without needing to do anything extra.
David Hill wrote:
As part of this Jira
are trying to make working in rt/apps easier.
To do that, we found that the only way to make the IDEs happy is be
to provide a common path to "host build" jfxrt.jar.
Currently we have:
which requires evaluation that Netbeans does not want to do.
We do need to support cross builds, so here is what we came up with,
explained here in the new improved comment from build.gradle
// The jfxrt task is responsible for creating the jfxrt.jar. A
// have multiple SDK's on their system at any one time,
// cross compiles they have done. For example, I might have:
// and so forth. The default host build will always install
// allowing for uses where a known sdk path is needed (like IDEs)
// This arrangement allows for multiple independent SDKs to
// exist on a developer's system.
After you sync, you will probably want to perform a clean build.
And then try out the apps, in the new easier to use format.
Note: for now, you will still need to specify the JDK for ant/nb, like