-
Notifications
You must be signed in to change notification settings - Fork 171
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
Support comments in jvm-opts file #66
Comments
I'd like to clarify a few more things about this bug report:
No, the version of
In mohiva/play-silhouette@bd17777, Travis script was customized to run with a more recent version of I didn't take time to identify the cause of the regression... But yeah, having automated tests/specs is the only way! As still unexperienced shellscripter and moreover non-native english speaker, I am not certain to fully understand last part of 73aba99 commit comment:
@paulp Do you want to support non-initial # comments or not? PS: This is great that |
"I ask because my original regexp-based implementation supported it..." Did it handle all the forms of quoting which might appear? The problem is if you want to pass a string containing a #, e.g. as part of a system property. Even if it did handle this - and it's really tricky with regexps - I find the feature unnecessary and prefer the implementation which doesn't take on baroque quoting issues. |
@gildegoma Indeed try your runner with a .jvmopts of
and you will see what I mean. |
Sure, I understand :)
You're right to correct me on this point. Sorry for writing this line too fast. I was not pretending my implementation was so robust, but I just wanted to be sure that we all agree to drop this feature. And fixing this weakness is actually a good argument to update the |
It wasn't exactly fixed until just now, but as of 4f44188 I believe it is. |
@paulp looks good! Thanks again for all your amazing work! |
Thank you @paulp and @gildegoma for looking into this. |
FYI: the JVM worker machine on Travis CI (.org) will be updated in the next days with 60b6f26. The exact rollout date will be announced on http://blog.travis-ci.com. Note that sbt 0.13.2 won't be pre-installed in this VM image, but in next VM update. |
When using a jvm-opts file with comments like this:
and a command line like this:
this error happens:
This situation will also happen when building on Travis CI, which uses this configuration:
For an example see this failed Travis CI build triggered by this script.
The text was updated successfully, but these errors were encountered: