java.library.path fix for MacOS X (7145798)
swingler at apple.com
Tue Feb 21 14:31:45 PST 2012
On Feb 21, 2012, at 2:28 PM, Michael Hall wrote:
> On Feb 21, 2012, at 4:07 PM, Mike Swingler wrote:
>> I think specifying a classpath should always root to things inside the bundle. Perhaps disallowing paths that start with "/" would make this very clear. The examples I've heard are apps that deploy using another shell as a framework (SWT, NetBeans-shell, etc), who are not willing/able to change their on-disk layout. The example I more sympathize with is accessing tools.jar, which is in the bundle, because it's in the JDK, but it's not on the classpath.
> Sorry, I did have a thought on this too. As Greg has recently been mentioning to me off-list
> -Djava.class.path might be a workaround to get too tools.jar.
> It would also be a workaround to point to any file anywhere on the machine wouldn't it?
That is a very bad workaround. If you need a tools.jar, it should ship in your bundle. If you don't copy it into the Contents/Java directory, you need a way to specify where else in your bundle it might be.
More information about the macosx-port-dev