Define aliases jython-latest & jython-release and rename jython-cli to jython

[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]

@jeff5 , I removed the "-cli" extension from all aliases. It is completely redundent.

Without this extension, running Jython feels more natural.

• jbang run jython@jython -V
• jbang run jython-latest@jython -V
• jbang run jython-release@jython -V

JBang allows aliases to be installed as a local app, for example:

$ jbang app install jython@jython

Thereafter jython is a new command that is available on the command-line.

$ jython -V
2.7.4

[wfouche]

@jeff5, all done, ready to be reviewed.

• Found a very simple workaround by using the support JBang already has to resolve LATEST and RELEASE version tags.
• Removed "-cli" from all aliases because it is overly cumbersome to use.