Re: Swing Look And Feel for Yosemite

2014-11-10 Thread Phil Race
On 11/10/14 9:45 AM, David DeHaven wrote: We still use it for the occasional generic "Java 7/8/9 on Mac" question that comes up from time to time. It is far preferable that the question be posted to the more specific lists, but sometimes it isn't clear where that belongs. There's enough of us

Re: MAS codesign requirements break Java app signing

2014-11-10 Thread Zach Oakes
I successfully am replacing the Info.plist file with the technique you mentioned. Is it possible that the JVMAppClasspath key does not actually do anything? I added the extra jars to it, trying both a space and a colon as a separator, and the java.class.path is always just the main jar file. Sorry

Re: MAS codesign requirements break Java app signing

2014-11-10 Thread Zach Oakes
With the Ant task, I already can manually edit my Info.plist so that's not an issue. The problem with it is simply that Apple is rejecting it after I upload the app with the error message I included in the OP. There is something wrong with the sig but I can't figure out what it is. On Mon, Nov 10,

Re: MAS codesign requirements break Java app signing

2014-11-10 Thread Alan Snyder
If you are using the Ant task, you may be able to get Ant to look for the resources using the classpath specified in the taskdef. However, that works only if the ant task JAR is not on Ant’s classpath. It took me a while to figure that out. > On Nov 10, 2014, at 1:10 PM, Danno Ferrin wrote:

Re: MAS codesign requirements break Java app signing

2014-11-10 Thread Danno Ferrin
You can insert values into the Info,plist, it just involves some acrobatics. There is a resource replacement technique that looks for the resource on the classpath of the execution of the tool, which for the CLI includes the current directory. There are also some peculiarities for the name. F

Re: MAS codesign requirements break Java app signing

2014-11-10 Thread Zach Oakes
Thanks Steve, I'll try it out when I get home. I am using 10.9.5 (Mavericks), not Yosemite. I'm using different entitlements under Danno's suggestion, and it has worked so far until some time in the last month. On Mon, Nov 10, 2014 at 3:29 PM, Steve Hannah wrote: > I was just reading through you

Re: MAS codesign requirements break Java app signing

2014-11-10 Thread Zach Oakes
Darn. Is there no way to manually insert values into the Info.plist before it is signed? If not, I guess I'll keep trying to get my custom script to work. I just need some kind of short term solution to get this app update out... By the way, I noticed there is also no way to set the CFBundleVersio

Re: MAS codesign requirements break Java app signing

2014-11-10 Thread Steve Hannah
I was just reading through your original codesign script for your infinikind bundler option, and I noticed that you are using different entitlements for the libs than for your app. I don't recall if entitlements are even required for the libs, but I have always just used the same entitlements for

Re: MAS codesign requirements break Java app signing

2014-11-10 Thread Danno Ferrin
This may be a bug in 8u20. By setting -Bclasspath= it should be putting in as the string. I'de have to dig up the code because that section of code is uner a major overhaul for 8u40 because of the new launcher work. On Nov 10, 2014, at 10:33 AM, Zach Oakes wrote: > I can see from the Info.

Re: Swing Look And Feel for Yosemite

2014-11-10 Thread David DeHaven
Since you're asking about Swing, it may be better to raise this on the swing-dev mailing list. >>> >>> I dont see why as the issue is very much specific to OSX >> >> Agreed, but I guess the Swing people unfortunately don't necessarily read >> this list.. > > I think there's a need

Re: MAS codesign requirements break Java app signing

2014-11-10 Thread Zach Oakes
I can see from the Info.plist file in the app bundle that JVMAppClasspath is an empty string: JVMAppClasspath On Mon, Nov 10, 2014 at 12:27 PM, Zach Oakes wrote: > It looks like the classpath is always just the main jar, no matter whether > I explicitly use -classPath or not. I am running > Sy

Re: MAS codesign requirements break Java app signing

2014-11-10 Thread Zach Oakes
It looks like the classpath is always just the main jar, no matter whether I explicitly use -classPath or not. I am running System.getProperty("java.class.path") and it returns "/path/to/myapp.jar" and nothing else. This is the current command I'm running: javapackager -deploy -native \ -name MyAp

Re: MAS codesign requirements break Java app signing

2014-11-10 Thread Zach Oakes
Oh, I didn't realize you could just put native libraries in srcdir. Is the classpath is set to .../Contents/Java as well? I have a few extra jar files my app needs to use. I can see they are copied there successfully, but I can't seem to find their classes on the classpath. On Mon, Nov 10, 2014 at

Re: MAS codesign requirements break Java app signing

2014-11-10 Thread Danno Ferrin
No, the class path is either set to all the files in the srcdir, or to whatever you explicitly set it to. Since you explicitly set the class path to -BclassPath=myapp.jar:ObjCBridge.jar:jna.jar then the class path is explicitly set. Note that with the javapackager everything passed in as a res

Re: Swing Look And Feel for Yosemite

2014-11-10 Thread Emmanuel Puybaret
>>> Since you're asking about Swing, it may be better to raise this on the >>> swing-dev mailing list. >> >> I dont see why as the issue is very much specific to OSX > > Agreed, but I guess the Swing people unfortunately don't necessarily read > this list.. I think there's a need for a clarifi

Re: MAS codesign requirements break Java app signing

2014-11-10 Thread Danno Ferrin
Is this a verification on the part of apple? Is it that the program does not find the library? Or is it that the native library is not in the .app package at all? For 8u20, the launcher javapackager provides sets the java.library.path to be /Contents/Java, so a call to System.loadLibrary(“jcoc

Re: Swing Look And Feel for Yosemite

2014-11-10 Thread Hendrik Schreiber
> I dont see why as the issue is very much specific to OSX Agreed, but I guess the Swing people unfortunately don't necessarily read this list.. -hendrik

Re: MAS codesign requirements break Java app signing

2014-11-10 Thread Zach Oakes
The error is the parameter dealing with the native library, libjcocoa.dylib, that my app requires. Does javapackager support adding native libraries? It should be copied into MyApp.app/Contents/MacOS. On Mon, Nov 10, 2014 at 10:41 AM, Zach Oakes wrote: > Ah, forgive me, there was an error in the

Re: Swing Look And Feel for Yosemite

2014-11-10 Thread Paul Taylor
On 10/11/2014 15:42, dalibor topic wrote: Hi, Since you're asking about Swing, it may be better to raise this on the swing-dev mailing list. cheers, dalibor topic I dont see why as the issue is very much specific to OSX Paul

Re: MAS codesign requirements break Java app signing

2014-11-10 Thread Zach Oakes
Ah, forgive me, there was an error in the bundle process so it stopped short of creating a pkg. I will keep working on the parameters to see if I can fix it. On Mon, Nov 10, 2014 at 10:38 AM, Zach Oakes wrote: > Definitely progress! It ended up creating a bundle, but not a pkg file. > Maybe it's

Re: Swing Look And Feel for Yosemite

2014-11-10 Thread dalibor topic
Hi, Since you're asking about Swing, it may be better to raise this on the swing-dev mailing list. cheers, dalibor topic On 20.10.2014 14:48, Emmanuel Puybaret wrote: Hi, OS X 10.10 Yosemite is out now and unless I missed something, Swing look and feel in new Java 7u72 / 8u25 wasn't prepar

Re: MAS codesign requirements break Java app signing

2014-11-10 Thread Zach Oakes
Definitely progress! It ended up creating a bundle, but not a pkg file. Maybe it's trying to make a normal mac bundle? I am using 8u25, by the way. On Mon, Nov 10, 2014 at 10:26 AM, Danno Ferrin wrote: > Try just '-native' and not '-native mac.appStore'. I think there were > case checking issue

Re: MAS codesign requirements break Java app signing

2014-11-10 Thread Danno Ferrin
Try just '-native' and not '-native mac.appStore'. I think there were case checking issues in the 8u20 release. On Nov 10, 2014, at 8:25 AM, Zach Oakes wrote: > Danno, since you mentioned javapackager, I decided to try using it in hopes > that it would solve the issue. I'm trying to put toget

Re: MAS codesign requirements break Java app signing

2014-11-10 Thread Zach Oakes
Danno, since you mentioned javapackager, I decided to try using it in hopes that it would solve the issue. I'm trying to put together a command for it, but it's a bit confounding. So far I'm just getting a jnlp and html file to appear. Here's what I have so far (split onto separate lines for readab