Set jython-cli version to RELEASE (latest stable version)

[wfouche]

@jeff5 , I think -dev is a more relevant suffice for the alias then -next given that this alias would typically refer to a development snapshot (pre-release).

[jeff5]

Not a development snapshot, technically: it would always be a beta or a release candidate, something worth publishing at Maven Central. Does that affect your choice of name?

It would be nice to stabilise this. Is there a convention elsewhere in the JBang ecosystem? If it's "-dev", fair enough.

I've noticed that the beta shows up as the "latest version" on Maven Central (questionably in my view). Is there maybe some way (a clean one please) to select the pre-final "latest" when the latest is not final, and ideally not involving the editing of the catalog each time?

[wfouche]

The "latest" and "release" versions can be determined by retrieving this XML file:

• https://repo1.maven.org/maven2/org/python/jython/maven-metadata.xml

[wfouche]

@jeff5 , thanks for the valuable feedback.

jython-cli-latest will now always use the latest Jython release.

$ jbang run jython-cli-latest@jython -V
Jython 2.7.5b1

[wfouche]

Alias jython-cli@jython will now always run the latest stable version of Jython which is the RELEASE version. If a different version of Jython is required, then set property -Djbang.jython.version=<version>.

$ jbang run jython-cli@jython -V
Jython 2.7.5b1

$ jbang run -Djbang.jython.version=2.7.4 jython-cli@jython -V
Jython 2.7.4

$ jbang run -Djbang.jython.version=LATEST jython-cli@jython -V
Jython 2.7.5b1

$ jbang run -Djbang.jython.version=RELEASE jython-cli@jython -V
Jython 2.7.5b1

[wfouche]

@jeff5 , @Stewori - please review and merge.