|
|
| Re: Hybrid jars [message #1234094 is a reply to message #1234085] |
Tue, 21 January 2014 08:18   |
 Lior Giller
Messages: 14
Registered: January 2014 |
Junior Member |
|
|
Hey Tom,
Thank you for the reply,
first i have changed the "Toolkit Type" == swing. it did not helped. the jar is still 300k, and i still get the
Process manager already initialized: can't fully enable headless mode.
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
for you second question, I'm not repackaging libs, I am exporting all the java sources and resources, than compress the jar.
exception when running. from Jar, when running from the e(fx)clipse all is still ok.
i wrote a new project just so i can find the issue since my project is very large,
i rewrote just the basics, something like a simple javafx project with a system tray app.
again, works well on the e(fx)clipse, but not as jar (except I don't get an error, the jar just doesn't do anything).
As I said before, my app is really big, and working well from the eclipse, so there must be something i'm doing wrong while packaging right?
I would hate to re do this whole thing just cause i cant get a proper jar 
ill appreciate any idea at this moment!!!
Thanks!
|
|
|
|
| Re: Hybrid jars [message #1234102 is a reply to message #1234094] |
Tue, 21 January 2014 08:38 |
Thomas Schindl
Messages: 6651
Registered: July 2009 |
Senior Member |
|
|
Hi,
IIRC the export is not packaging the libraries directly into the JAR but
adds a MANIFEST.MF-Entry pointing to them, not?
I'd need something to test to see what's broken. In the end all our
build is doing is to write the build.xml and execute it. You can take a
look at the build.xml and fix things manually?
Tom
On 21.01.14 09:18, Lior Giller wrote:
> Hey Tom,
>
>
> Thank you for the reply,
>
> first i have changed the "Toolkit Type" == swing. it did not helped. the
> jar is still 300k, and i still get the Process manager already
> initialized: can't fully enable headless mode.
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> for you second question, I'm not repackaging libs, I am exporting all
> the java sources and resources, than compress the jar.
> exception when running. from Jar, when running from the e(fx)clipse all
> is still ok.
> i wrote a new project just so i can find the issue since my project is
> very large, i rewrote just the basics, something like a simple javafx
> project with a system tray app. again, works well on the e(fx)clipse,
> but not as jar (except I don't get an error, the jar just doesn't do
> anything).
>
>
> As I said before, my app is really big, and working well from the
> eclipse, so there must be something i'm doing wrong while packaging right?
> I would hate to re do this whole thing just cause i cant get a proper
> jar :(
> ill appreciate any idea at this moment!!!
>
> Thanks!
|
|
|
|
|
|
|
| Re: Hybrid jars [message #1234173 is a reply to message #1234129] |
Tue, 21 January 2014 11:54 |
Lior Giller
Messages: 14
Registered: January 2014 |
Junior Member |
|
|
I have some progress which might help understand the issue better.
i realised (and maybe it was obvious but i missed it( that fro running from e(fx)clipse, i use "main" method., but if i want my jar to work, i need to use "start" method.
i manages to get my simple system tray app working by copying my "main" code into the start, but from eclipse its stopped cause i have to have main.
thats why i fail running as javafx jars, as it searches for the start method.
also, on my mac, when i'm running from main all is ok, but same code running from start i get different result for
if (!SystemTray.isSupported()) {
System.out.println("SystemTray is not supported");
return;
running from eclipse- its supported, running from jar its not.
Does that make any sense to you?
Lior
|
|
|
| Re: Hybrid jars [message #1234191 is a reply to message #1234173] |
Tue, 21 January 2014 12:41 |
Thomas Schindl
Messages: 6651
Registered: July 2009 |
Senior Member |
|
|
If you look at the MANIFEST.MF generated? Does it hold the special
JavaFX-Launcher as the main-class?
If I remember correct JavaFX-Launcher does not call main but directly
bootstraps the application class and calls the start method.
What makes me wonder a bit because you said you have a Swing application!
Tom
On 21.01.14 12:54, Lior Giller wrote:
> I have some progress which might help understand the issue better.
> i realised (and maybe it was obvious but i missed it( that fro running
> from e(fx)clipse, i use "main" method., but if i want my jar to work, i
> need to use "start" method. i manages to get my simple system tray app
> working by copying my "main" code into the start, but from eclipse its
> stopped cause i have to have main.
> thats why i fail running as javafx jars, as it searches for the start
> method. also, on my mac, when i'm running from main all is ok, but same
> code running from start i get different result for if
> (!SystemTray.isSupported()) {
> System.out.println("SystemTray is not supported");
> return;
>
> running from eclipse- its supported, running from jar its not.
>
> Does that make any sense to you?
>
> Lior
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.57230 seconds
] 
Search
Help
Register
Login
Home
