-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
FR: link to the latest jabref-4.0.*.jar #2953
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" <[email protected]>:
… 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
<#2953 (comment)>, 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" <[email protected]>:
… 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" ***@***.***
>:
> 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
> <#2953 (comment)>,
or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/
AATi5MG2N5YYc8Jk4qFKrBZ2Ofw7blAAks5sJLKegaJpZM4OKSlE>
> .
>
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#2953 (comment)>, 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 2ec520f. 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? |
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
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 tohttps://builds.jabref.org/master/JabRef-4.0.0-dev--snapshot--2017-06-29--master--7e50e84a1.jar
and so onThe text was updated successfully, but these errors were encountered: