how to decide to put jars in fiji/jars/ or /fiji/plugins/

110 views
Skip to first unread message

Tobias Pietzsch

unread,
Apr 10, 2014, 6:29:54 PM4/10/14
to Johannes Schindelin, fiji-devel Developers
Hi Dscho,

What is the rationale behind putting jars in either fiji/jars/ or /fiji/plugins/?

Background: I'm just about to upload a new BigDataViewer version to my update site and I'm wondering where to best place the jars.
I have third-party jars, like jdom2.jar, I guess these should go to fiji/jars/, right?
But now I also have split up BDV itself into multiple jars, one for the core, and one for the fiji plugins. Should they both go to fiji/plugins/?

best regards,
Tobias
signature.asc

Johannes Schindelin

unread,
Apr 11, 2014, 10:45:48 AM4/11/14
to Tobias Pietzsch, fiji-devel Developers
Hi Tobias,

On Fri, 11 Apr 2014, Tobias Pietzsch wrote:

> What is the rationale behind putting jars in either fiji/jars/ or
> /fiji/plugins/?

ImageJ 1.x determines that a .jar file contains plugins by the telltale of
an underscore in its file name. If a plugins.config is found inside the
.jar file, it is then parsed, if there is no such file, all the contained
classes having an underscore in their name are considered to be plugins.

Now, this is slightly error prone: who is to say that completely
independent Java libraries do not have underscores in their file *and*
class names?

And that is exactly what happened: jai_codec.

ImageJ 1.x now has a work-around (which is not quite complete; it is
probably a matter of time until an edge case falls through the
work-around's cracks), but the safe way for Fiji was to put all the
libraries into jars/ and all the .jar files containing plugins into
plugins/.

Ciao,
Johannes

P.S.: Please feel more than free to take this information, put it into
your own words and enhance the FAQ on the Fiji Wiki. That way, the
documentation does not depend on yours truly only.

Tobias Pietzsch

unread,
Apr 11, 2014, 11:54:38 AM4/11/14
to Johannes Schindelin, fiji-devel Developers
Done. Thanks!
signature.asc
Reply all
Reply to author
Forward
0 new messages