Ticket #1851 (closed defect: fixed)

Opened 6 years ago

Last modified 6 years ago

Fix Fiji issues with sezpoz

Reported by: dscho Owned by: dscho
Priority: major Milestone: imagej2-b7-ndim-data
Component: Core Version:
Severity: serious Keywords:
Cc: curtis Blocked By:
Blocking: #1608, #1729

Description

Every since fiji-compat depends on scijava-common, there is a problem with sezpoz: basically, any plugin implementing an interface defined in ij-[a-z]*.jar fails, including the updater's UploaderService and the Help>Upload Sample Image command.

The issue has been addressed in  https://java.net/jira/browse/SEZPOZ-14 but not merged upstream yet (to be fair, the bug is only 5 days old now, even if it offers an easily applyable patch series ready to go). Since the problems persist until we upload a new sezpoz version, deploy a new, IJ2-specific, sezpoz version and upload that to the ImageJ update site.

Change History

comment:1 Changed 6 years ago by dscho

  • Cc curtis added
  • Status changed from new to closed
  • Resolution set to fixed

I deployed sezpoz-1.9-imagej via scijava-common's release-version.sh (and updated  https://github.com/dscho/sezpoz accordingly).

Then I bumped the SciJava POM version (actually twice because I first had to update it to reflect the new sezpoz version and then the new scijava-common version).

After that, I uploaded the relevant files to the ImageJ update site.

Unfortunately, a further change in Fiji was necessary: since the Class-Path: entry in fiji-compat no longer reflected the correct file names, I had to upload a new one. Unfortunately, the updater ignores the Class-Path: entries when calculating the checksum, so I just merged an early part of the ij-legacy branch to make fiji-compat really different to be able to download it.

But now uploading (both to an update site and to ImageJ's sample uploader) works again!

comment:2 Changed 6 years ago by dscho

Aaargh! I just realized that I failed to use 1.9.1-imagej as we agreed upon. Bah! Will pay more attention next time. Sorry!

Note: See TracTickets for help on using tickets.