Tracking down an NPE
zonski at gmail.com
Mon Jun 10 15:38:06 PDT 2013
Cool, thanks - so the native packager requires that every one of the JARs
used in the app (even the third party ones not built as part of the app)
have a manifest in them? That's going to be very nasty.
Regarding getting the javafx-ant jars into a repo, I started down this road
a while back and have now access to the OSS repo for groupID
I gave up actually deploying it when I realised there was a different
javafx-ant.jar for each native platform. I wasn't able to build them all
(and the Windows build was patchy at best anyway).
Happy to work with you on getting them into that repo if you want. Just let
me know where you're up to with it and what you need.
On Tue, Jun 11, 2013 at 8:27 AM, Danno Ferrin <danno.ferrin at shemnon.com>wrote:
> At least one of your jars does not have a manifest:
> I'm tempted to get the JFX78 builds auto-deploying at least the javafx-ant
> jar to some repo so the build plugins can use JavaFX 8 deployment code on
> Java 7.
> On Mon, Jun 10, 2013 at 4:13 PM, Daniel Zwolenski <zonski at gmail.com>wrote:
>> Any chance someone from Oracle could tell me what the line of code is in
>> com.sun.javafx.tools.packager.bundlers.BundleParams at line 390?
>> Someone is getting a NullPointer on this line when using the maven plugin
>> and I can't work out why. The line number is different in the Sun code vs
>> the open sourced one.
More information about the openjfx-dev