Jabref: FR: link to the latest jabref-4.0.*.jar

Created on 30 Jun 2017  Â·  7Comments  Â·  Source: JabRef/jabref

could you provide a link / symlink to the latest jabref-4.0.*.jar, please?
It would be very nice, if users can use a bash script like
UpdateJabref.sh

#!/bin/bash
wget https://builds.jabref.org/master/JabRef-4.0.0-dev--snapshot--latest.jar

which fetches the latest .jar.
Upstream has just to provide https://builds.jabref.org/master/JabRef-4.0.0-dev--snapshot--latest.jar which links to https://builds.jabref.org/master/JabRef-4.0.0-dev--snapshot--2017-06-29--master--7e50e84a1.jar and so on

build-system documentation

All 7 comments

The script to modify is upload-to-builds.jabref.org.sh. Do you have an idea how to implement that using sftp commands?

Maybe this can be done by providing a symlink?
I have no idea how to code that, but I think this could work

Am 30.06.2017 10:32 vorm. schrieb "Oliver Kopp" notifications@github.com:

The script to modify is upload-to-builds.jabref.org.sh
https://github.com/JabRef/jabref/blob/master/scripts/upload-to-builds.jabref.org.sh.
Do you have an idea how to implement that using sftp commands?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/JabRef/jabref/issues/2953#issuecomment-312209038, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AATi5MG2N5YYc8Jk4qFKrBZ2Ofw7blAAks5sJLKegaJpZM4OKSlE
.

Sure, but the target of the symblink changes at each update. And AFAIK, it
is not possible to use "wildcard symlinks".

Am 30.06.2017 11:42 schrieb "Christoph" notifications@github.com:

Maybe this can be done by providing a symlink?
I have no idea how to code that, but I think this could work

Am 30.06.2017 10:32 vorm. schrieb "Oliver Kopp" <[email protected]

:

The script to modify is upload-to-builds.jabref.org.sh
upload-to-builds.jabref.org.sh>.
Do you have an idea how to implement that using sftp commands?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/JabRef/jabref/issues/2953#issuecomment-312209038,
or mute
the thread
AATi5MG2N5YYc8Jk4qFKrBZ2Ofw7blAAks5sJLKegaJpZM4OKSlE>
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/JabRef/jabref/issues/2953#issuecomment-312211263, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABTafvfaOTxEILsHNjpsYmLFhXYNtxIVks5sJLUJgaJpZM4OKSlE
.

Maybe we should just use the install4j auto updater for the development version. I think this really makes sense since we get quite a lot of bug reports recently that are already fixed in master.

Implemented via https://github.com/JabRef/jabref/commit/2ec520fd05523f5c3d7ad9b355e77a93a0a1d99a. Not using bash as the builds are done at CircleCI (see https://github.com/JabRef/jabref/wiki/CI) and I did not want to install and maintain icrond.

http://builds.jabref.org/master/JabRef--master--latest.jar now always links to the latest file.

@koppor should we also put the link on the main homepage?

Was this page helpful?
0 / 5 - 0 ratings

Related issues

tobiasdiez picture tobiasdiez  Â·  4Comments

LinusDietz picture LinusDietz  Â·  3Comments

caugner picture caugner  Â·  3Comments

lenhard picture lenhard  Â·  4Comments

oscargus picture oscargus  Â·  3Comments