Winstone uses cached version of Hudson even if new one is given on the command line

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      I use Hudson with the included Winstone container ('java -jar hudson.war') on
      Windows XP (from the command line, not as a service).

      When I update Hudson to a new version, Winstone apparently ignores the new war
      and still uses the old one from the temp directory (C:\Document and
      Settings\myuser\Local Settings\Temp). Replacing means of course: shutdown
      Hudson, replace the war, restart.

      This can be verified by the version number in the bottom right of the web page
      http://localhost:8080/ , which doesn't change.

      In order to activate the new one, it is necessary to remove the directory
      C:\Document and Settings\myuser\Local Settings\Temp\winstone , which contains
      the extracted war.

      Version details: The first one, 1.184, remained active even though I replaced
      the war successively with 1.185, 1.190 and 1.193.

            Assignee:
            Unassigned
            Reporter:
            hok
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: