Allow users to specify the WorkingDirectory for OSX app plist files #8
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Neurogami
added a commit
that referenced
this pull request
May 17, 2012
…plist Allow users to specify the WorkingDirectory for OSX app plist files
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In my project we rely the working directory to be the same as it is on Windows or when using the JAR (where the *.exe or *.jar file resides)
Since OSX generates .app files this is not the case (the working directory is the directory which contains the .app directory
In our case we rely on it so we can load a static data file (lib/countries.yml) which is specified with the
files_to_copyoption.I've added a new option
mac_plist_working_directorywhich will specify the value WorkingDirectory key in the plist file. This will default to $APP_PACKAGE which is Apple's default value for this key, which will ensure backwards compatibility.https://developer.apple.com/library/mac/#documentation/Java/Reference/Java_InfoplistRef/Articles/JavaDictionaryInfo.plistKeys.html