Conversation
Member
Author
|
@jeff5 , jython-cli does not currently work with the latest release of JBang (0.139.3). This fix resolves the issue. |
Member
Author
Member
Author
|
JBang 0.141.0 has just been released, and resolved this issue that this PR solves. PR no longer required. |
This file contains hidden or 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
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.
JBang versions after 0.138.0 do not support the previously "not officially supported but working anyway" way of specifying runtime options that JythonCli.java uses for readability purposes.
No longer can we specify options using the following syntax:
--runtime-option -Dpython.console.encoding=UTF-8The
--<option>=<value>format must be used. The format changes to:--runtime-option=-Dpython.console.encoding=UTF-8which can be shortened to :
-R=-Dpython.console.encoding=UTF-8The same update has been applied to options
--depsand--main.