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: |
|
| Component: | Other | Version: | |
| Severity: | serious | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | #1563 |
Description
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
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.
dscho, please associated with some feature ticket