That's a clever use of the standard extensions class loader.
Yeah, but after I thought about, I believe adding a Class-Path
attribute to
the app's manifest is a better strategy.
Okay dokey.
I actually tried to run a very simple class that just printed an
entry to the console and references no other classes, just put it in
the classpath, and double-clicked on the app. It failed, too.
I think you may have missed my point. If your Info.plist ClassPath
is very
long, then it doesn't matter whether your app-jar is just a single
HelloWorld class or not.
No worries -- that is exactly what I tried -- removing everything but
the one JAR containing the one class.
By the way, what was your command-line when it worked? Did it also
have a
long classpath? If so, did it use relative or absolute pathnames?
java -cp cms.jar:[the whole mess of jars here] com.dtsoft.cms.CMSApp
That was generated by my IDE; I just copy and pasted it into the
command-line.
You could try something more systematic, such as pointing
CFBundleExectuable to a shell script with chmod a+x, just to see if
it's
launching. If so, then you know it's not Launch Services.
Hey, great idea.
Hey, how does Launch Services uniquely identify an app? I assume not
by file name but by some identifier in Info.plist, yeah?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
