Ticket #2039 (closed defect: moved)
Opened 2014-01-16T12:20:55-06:00
Last modified 2014-04-30T07:22:19-05:00
Updater cannot upload unchanged JARs with new version
| Reported by: | curtis | Owned by: | dscho |
|---|---|---|---|
| Priority: | major | Milestone: | imagej-2.0.0 |
| Component: | Updater | Version: | |
| Severity: | serious | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: |
Description
There is a limitation in the ImageJ Updater's support for version numbers. If a JAR file compares equal to the current version, but has a different filename, it is not flagged as locally modified. You can tell the updater to upload the JAR anyway via right-click and "Upload to XYZ" action. However, if you do this and proceed with the upload, the operation ends in a failure stating that the JAR has already been uploaded.
Hence, it is not possible to upload a new version of a JAR file when the actual contents of the JAR are unchanged. This leads to confusion for users who peek into the jars and/or plugins folders, because e.g. in the case of Bio-Formats, they see a mixture of files labeled as 4.4.10 (latest release at time of this writing) and older releases such as 4.4.9. This has already come up at least once on the mailing list, and will continue to cause confusion until there is a way to update the version numbers on the update site.