Re: problem with using external jar-files with the "compile and run" command
Posted by Robert Dougherty on Jan 16, 2006; 5:10pm
URL: http://imagej.273.s1.nabble.com/problem-with-using-external-jar-files-with-the-compile-and-run-command-tp3704060p3704067.html
> The following hint made my plugins work correctly:
>
> "If you are using the JRE that comes with ImageJ, it's in the lib\ext
> directory of that installation."
>
> I'm a windows user and so I copied Jama-1.0.2.jar to
> C:\Programme\ImageJ\jre\lib\ext
>
It works for me too. It would have been easier to try Duane's suggestion
first.
> this looks like a bug in the current version of Jama(?) I use
> Jama-1.0.1.jar calling it from a plugin without problems.
For Jama-1.0.0 and Jama-1.0.1 it works to copy the source folder, with its
precompiled classes, to the ImageJ plugins folder. The strange error
"invalid constant type: 13" seems to be new with Jama-1.0.2. But the .jar
version, properly placed in the ImageJ\jre\lib\ext, does work. So what
gives? Comparing the .class files from the .jar and the .class files from
source folder (.zip), they do not match in size, so something may have gone
wrong in the Jama-1.0.2 release packaging. The other problem I addressed in
my long installation seems to be an inability of ImageJ's compile and run
command to look down more than one level from the plugins folder. This has
been discussed recently, but I have not been able to find it.
Bob