Ticket #1626 (closed defect: duplicate)
Opened 2013-01-14T11:49:21-06:00
Last modified 2013-04-15T00:02:36-05:00
Sezpoz error on Windows
| Reported by: | bdezonia | Owned by: | dscho |
|---|---|---|---|
| Priority: | major | Milestone: |
|
| Component: | Core | Version: | |
| Severity: | serious | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | #1207 |
Description
During startup code of ImageJ2 on Windows there are multiple exceptions related to SezPoz that are thrown. They all have the following signature:
java.lang.ClassNotFoundException: com.sun.tools.apt.Main
at java.net.URLClassLoader$1.run(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at imagej.util.CheckSezpoz.fix(CheckSezpoz.java:368)
at imagej.util.CheckSezpoz.checkDirectory(CheckSezpoz.java:158)
at imagej.util.CheckSezpoz.check(CheckSezpoz.java:122)
at imagej.util.CheckSezpoz.check(CheckSezpoz.java:108)
at imagej.ImageJ.<init>(ImageJ.java:213)
at imagej.ImageJ.<init>(ImageJ.java:171)
at imagej.ImageJ.<init>(ImageJ.java:161)
at imagej.Main.launch(Main.java:59)
at imagej.Main.main(Main.java:74)
Change History
comment:1 Changed 2013-01-14T17:38:02-06:00 by dscho
comment:2 Changed 2013-01-15T10:00:10-06:00 by bdezonia
Yes, I was running from within Eclipse on Windows and only with the JRE. I was doing a quick build to test some code.
comment:3 Changed 2013-03-19T11:24:39-05:00 by bdezonia
- Status changed from new to reviewing
dscho, please associated with some feature ticket
comment:4 Changed 2013-03-19T14:28:22-05:00 by dscho
- Blocking 1207 added
This is not really a bug, but it was a PEBCAK. Still, I can add code to point that out better.
That is not all there is to it, right?
1) I suspect you run this inside Eclipse, not from a regular Imagej.app/ directory, and
2) you asked Eclipse to run this with the *JRE* rather than the *JDK*.
If so, we should probably catch the Error and suggest to the user to run with the JDK instead since we cannot guarantee correct artifacts otherwise (and endless frustration on both their and our sides would ensue).