AppBundler: wrong working directory
swingler at apple.com
Wed Feb 29 17:56:43 PST 2012
On Feb 29, 2012, at 7:56 AM, Greg Brown wrote:
>>> <option value="-Duser.dir=Contents/Resources"/>
>> That is less onerous for developers to adopt, but it's quite a subtle thing which is not self-documenting.
> Perhaps, but macro expansion isn't really self-documenting either.
Well, the name of the macro should explain what it expands to. If it doesn't, it has a bad name.
> I actually had no idea until I looked at the source code for the earlier launcher that it was even supported. Plus, it's pretty easy to document that the default working directory for a bundled app is the bundle root. As a developer, you might even assume this.
How could the developer assume where the root is? The .app bundle, the Contents/ directory, or the Contents/Java directory?
>> I'd still advocate for macro expansion (and I'd be happy to provide a diff) if that's a direction you'd support as well.
> I'd prefer to stick with the idea of setting the default working directory to the bundle root for now. It seems like it would address all of the issues that have come up so far and is less complex than adding macro support.
That's reasonable. I'm sure if setting the CWD alone is insufficient, someone will speak up. :-)
More information about the macosx-port-dev