NOTICE! This is a static HTML version of a legacy ImageJ Trac ticket.

The ImageJ project now uses GitHub Issues for issue tracking.

Please file all new issues there.

Ticket #1549 (closed defect: fixed)

Opened 2012-10-24T09:28:57-05:00

Last modified 2013-06-04T12:17:13-05:00

Start even when ij.jar is corrupted or not present

Reported by: dscho Owned by: dscho
Priority: minor Milestone: imagej2-b7-ndim-data
Component: Other Version:
Severity: serious Keywords:
Cc: Blocked By:
Blocking: #1563


When there is a corrupted ij.jar (or on MacOSX a too-old version in /Library/Java/Extensions/ or /System/Library/Java/Extensions/), the legacy service fails to runtime-patch IJ1. That's okay. But it should fail gracefully and not prevent IJ2 from starting.

To avoid confusion, we should even tell the user when such a thing happens, which we can do by using the ClassUtils to check the location of ij.jar.

Change History

comment:1 Changed 2013-03-19T11:23:17-05:00 by bdezonia

  • Status changed from new to reviewing

dscho, please associated with some feature ticket

comment:2 Changed 2013-03-20T12:08:59-05:00 by bdezonia

  • Blocking 1563 added

comment:3 Changed 2013-04-03T13:48:32-05:00 by bdezonia

  • Priority changed from major to minor

comment:4 Changed 2013-06-04T12:17:13-05:00 by dscho

  • Status changed from reviewing to closed
  • Resolution set to fixed

Somewhere along the line, this got fixed. I think it was when we switched the DefaultPluginService to handle non-starting services gracefully, logging a warning only.