[ImageJ-devel] importing custom "uncompressed" libraries (i.e., no JAR)

Curtis Rueden ctrueden at wisc.edu
Fri Sep 12 12:19:24 CDT 2014


Hi Gaetano,

> In my brand new Fiji installation, I can import my library only if I
> archive all .class files into a JAR file.

IIUC, what you describe is still supposed to work.

Could you please provide a minimal, complete, verifiable example
demonstrating the issue?

http://imagej.net/Bug_reporting_best_practices

Regards,
Curtis

On Fri, Sep 12, 2014 at 6:05 AM, Gaetano Impoco <gaetano at impoco.it> wrote:

> Dear all,
> I developed a custom library for my own convenience that used to work in
> ImageJ1.x. In my old IJ1 installation I used to add the library root
> directory
> to the Java CLASSPATH (using a simple bash script).
> In my brand new Fiji installation, I can import my library only if I
> archive all
> .class files into a JAR file. I would like to use JARs only for
> deployment. Is
> there any way to include the "uncompressed" (development version) library?
>
> Thank you
> Gaetano
>
>
>
> _______________________________________________
> ImageJ-devel mailing list
> ImageJ-devel at imagej.net
> http://imagej.net/mailman/listinfo/imagej-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://imagej.net/pipermail/imagej-devel/attachments/20140912/310c833b/attachment.html>


More information about the ImageJ-devel mailing list