http://imagej.273.s1.nabble.com/shared-java-classes-tp5019984p5020095.html
Replying to this thread for the archives. The discussion happened on a
> I'm starting to have problems with multiple versions of (usually
> identical, sometimes not) Java classes used
> by installed plugins. I could use some advice on how to best deal with
> this.
>
> For example - suppose I have two plugins, both of which use a collection
> of 5 Java Classes.
>
> My current methodology is to share source code - putting a copy of the
> shared .java files in both development directories, and the resulting
> .class files end up in both .jar files (which I then drag&drop to install
> in FIJI).
>
> This is never a problem, until I upgrade one or more of the same shared
> classes. Then, it seems like a crap shoot to determine which class gets
> used by a particular plugin.
>
> So..what's the best method of using just ONE copy of a shared set of
> classes?
>
> My development environment is: emacs, ant. The usual drill is to package
> up each plugin in it's own .jar file, which is drag&dropped into FIJI. I
> almost never get a complaint about duplicates - but I do see cases where
> the "wrong" version is used in a particular plugin. My fix at the moment
> is to un-install all of the old plugins, distribute the latest versions of
> a helper package to all the plugins that need it, and then re-installing
> these plugins in FIJI.
>
> --
> Kenneth Sloan
>
[hidden email]
> Vision is the art of seeing what is invisible to others.
>
> --
> ImageJ mailing list:
http://imagej.nih.gov/ij/list.html>