Re: [javaCompiler-users] Request for AWT information
Status: Beta
Brought to you by:
soapy
From: Lee D. P. <le...@3s...> - 2007-01-01 17:58:39
|
Forgot to add: I have two jar files that only contain resources and not any .class files. The jar file that contains text resources in the form of .properties files compiles without error, it's just the jar file that contains the images that fails (they are GIFs and ICO files). Lee -----Original Message----- From: jav...@li... [mailto:jav...@li...] On Behalf Of Lee D. Painter Sent: 01 January 2007 17:55 To: A mailing list for general questions and discussions. Subject: Re: [javaCompiler-users] Request for AWT information Marco, I have now been able to compile and test a native build of our application and all functionality is working as expected but there is one issue that will presently stop us using this in production. When displaying images that are compiled into the .exe they are corrupted.=20 You can see this for yourself. Original Java Runtime: http://3sp.com/Q38CEW924W/1.GIF Native Compiled .exe: http://3sp.com/Q38CEW924W/2.GIF Is this a known issue? To workaround the problem I thought it would be possible to reference a jar file instead of compiling it into the .exe as this jar file only contains image resources. However if I uncheck the relevant jar file in the archive section of the JNC GUI I get the following error on compile: creating "Agent.exe" for Windows - processing agent-resources.jar failed: java.io.FileNotFoundException: C:\DOCUME~1\lee\LOCALS~1\Temp\JNCTempti0w8q.out\archive.a: The system cannot find the file specified. Any insight you could provide would be appreciated. Regards Lee -----Original Message----- From: jav...@li... [mailto:jav...@li...] On Behalf Of Marco Trudel Sent: 22 December 2006 13:58 To: A mailing list for general questions and discussions. Subject: Re: [javaCompiler-users] Request for AWT information Lee D. Painter wrote: >> I assume that the properties have spaces, right? >=20 > No, the properties I'm adding are: >=20 > -Dcom.averick.ssl.allowUntrustedCertificates=3Dtrue > -Dcom.maverick.ssl.allowInvalidCertificates=3Dtrue >=20 > It looks to me like these are being included on the compilation step for > the jar and only need to be included on the final main build step. You are right. I assumed that all flags are for jar compilation and the=20 main compilation. But of course there exist flags that are only for the=20 main compilation (but none that are only for jar compilation). I added it to my todo-list for version 1.1 since this is not a mayor=20 problem. You can work around that by: 1. Compile your application without the flags. The compiled jars will be cached and reused in further compilations. 2. Add the flags and compile again. This is only bad if the jars change between every native compilation=20 step. But that is very unlikely (I assume). Is that ok for you? Else I can put it higher in my priority list :-) Marco ------------------------------------------------------------------------ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDE V _______________________________________________ javaCompiler-users mailing list jav...@li... https://lists.sourceforge.net/lists/listinfo/javacompiler-users ------------------------------------------------------------------------ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDE V _______________________________________________ javaCompiler-users mailing list jav...@li... https://lists.sourceforge.net/lists/listinfo/javacompiler-users |