-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.boot-env file causing errors when starting from uberjar #80
Comments
I have had a quick look at the source - I think this line may not be correct. If I eval something like I think if you use |
See #81 |
It looks like this is caused by |
Oh right, I thought the intention was that .boot-env would be read from the jar file (so you'd ship the defaults baked into the jar but then replace them with env vars or whatever). I will fix my pull request in a sec. |
Previously, classpath resources were assumed to be files and passed to io/file. This failed when the resource was within a jar. The fix is to use io/reader instead, which works on resources within or without jars. Fixes: weavejester#80
I haven't been able to get boot-environ working with a simple uberjar. Attached is a minimal example of what happens:
environ-bug.zip
If I run this with
I get an exception
Whereas I expect it to print "spork" and exit.
The text was updated successfully, but these errors were encountered: