Details
-
Type:
Improvement
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Webstart
-
Labels:None
-
Urgency:Not urgent
Description
Mark Saper noted that when Jalview updates that involve changes in dependencies are released, people who launch Jalview using a local JNLP have to fix their JNLP before Jalview will work correctly.
Ideally, once someone generates a JNLP with a specific set of launch settings, it should work regardless of which jalview version is currently available.
See comment below from (http://www.jalview.org/pipermail/jalview-discuss/2014-June/001024.html)
On 12/06/2014 14:30, Mark A Saper wrote:
> I traced the problem to my jalview.jlnp file that I use to launch jalview. Although Java downloaded the new jalview 2.8.1 I continued to launch jalview with a jalview.jnlp file that I have in my /Applications folder which had reference to the older version of JABAWS.
Well done for working that out !
> This has happened several times before over the years. How can always launch the program with the most recent jalview? Use a link?
Ideally, once someone generates a JNLP with a specific set of launch settings, it should work regardless of which jalview version is currently available.
See comment below from (http://www.jalview.org/pipermail/jalview-discuss/2014-June/001024.html)
On 12/06/2014 14:30, Mark A Saper wrote:
> I traced the problem to my jalview.jlnp file that I use to launch jalview. Although Java downloaded the new jalview 2.8.1 I continued to launch jalview with a jalview.jnlp file that I have in my /Applications folder which had reference to the older version of JABAWS.
Well done for working that out !
> This has happened several times before over the years. How can always launch the program with the most recent jalview? Use a link?