NOTICE! This is a static HTML version of a legacy Fiji BugZilla bug.

The Fiji project now uses GitHub Issues for issue tracking.

Please file all new issues there.

Bug 585 - Update for ImageJ-win-64.exe fails.
Update for ImageJ-win-64.exe fails.
Status: RESOLVED WORKSFORME
Product: Fiji
Classification: Unclassified
Component: ImageJ2
unspecified
PC Windows
: P5 critical
Assigned To: ImageJ Developers Mailing List
Depends on:
Blocks:
 
Reported: 2013-04-11 15:56 CDT by cjhirsch
Modified: 2013-04-23 12:15 CDT
1 user (show)

See Also:

Description cjhirsch 2013-04-11 15:56:15 CDT
When trying to upload the new IMAGEJ-win-64.exe, it requires ij,jar, which does not exist.  The update fails.
Comment 1 Johannes Schindelin 2013-04-12 10:17:04 CDT
Do you mean you try to update it? I ask because you would get permission problems if you tried to upload it: we cannot just allow everybody to upload new versions of core ImageJ files...
Comment 2 Johannes Schindelin 2013-04-12 12:18:01 CDT
From a mail reply:

Yes, I was trying to update ImageJ.  I followed the directions to  some files since the updater was not working,
" Unfortunately, there was a bug in the ImageJ updater that affected the update of the updater itself. The easiest way to get back a functional updater is to import this URL via File>Import>URL....
If that does not work, please delete the files ij-ui-swing-updater-2.0.0-SNAPSHOT.jar, ij-updater-core-2.0.0-SNAPSHOT.jar and ij-core-2.0.0-SNAPSHOT.jar from the Fiji.app/jars/ directory (MacOSX users, Ctrl-click on the Fiji icon and select Open Package Contents and open            
thejars/ directory you see there). After that, the Updater should magically repair itself."
 and then tried updating.  Things still did not work, so I went to the site that was indicated to get the newest version for updating, launched it and this problem came up.
"If that still fails, please download a fresh copy from here:
Download
We have continuous releases thanks to ImageJ's Jenkins server:"
Please tell me if I am doing something incorrectly.  I was certainly not interested in getting something that is not for general use.
Carol
Comment 3 Johannes Schindelin 2013-04-12 12:28:13 CDT
Hi Carol,

it is good that you specified exactly the steps you performed because that was not clear from the original bug report. Based on the original account, I had chased around for 30 minutes before I gave up and admitted to myself that I failed at reproducing your issue.

Unfortunately, even after the additional report, I am unable to reproduce. This time, I just followed the following steps:

- downloaded a .zip from http://jenkins.imagej.net/job/Stable-Fiji/lastSuccessfulBuild/artifact/fiji-win64.zip

- unpacked it onto the Desktop

- ran ImageJ-win64.exe from there

- it wanted to update ij-core, which I let it do.

- restarted as suggested

- called up the updater again

- it said "up-to-date!"

As I spent already some time on this issue today, I might have to shift additional endeavors to fix your problem to another day, based on your feedback.

For the record: it would be good if you sent your response by logging in to http://fiji.sc/bugzilla/﷒0﷓. Our BugZilla is not set up to understand response mails.
Comment 4 Johannes Schindelin 2013-04-23 12:15:55 CDT
It does work for me.