Posted by
Burger Wilhelm on
Feb 05, 2015; 8:25pm
URL: http://imagej.273.s1.nabble.com/Update-site-with-multiple-plugin-versions-tp5011460p5011464.html
Hello Curtis,
thanks much for you instant advice!
The plugins for all book editions are in fact compatible with the most recent version and we do have control over (and use) the package structure. We wrapped each edition into a separate JAR file which contains a distinct Java package for each book chapter. Thus -- Java-wise -- all book editions could coexist peacefully together in one plugins folder (though this would create an overly long menu list). However, ImageJ's plugin loader seems to check for identical class names and disregards the package structure, consequently raising duplicate plugin errors when two editions (with identical plugin names) are present at the same time.
I believe the best solution is, as you suggested, to set up a specific update site for each edition.
Thanks much again,
Wilhelm
www.imagingbook.com<
http://www.imagingbook.com/>
___
PS: Our complete ImageJ code is also available at SourceForge now (see
http://sourceforge.net/projects/imagingbook).
________________________________
From:
[hidden email] [
[hidden email]] On Behalf Of Curtis Rueden [
[hidden email]]
Sent: Thursday, February 05, 2015 19:34
To: Burger Wilhelm
Cc: ImageJ Interest Group
Subject: Update site with multiple plugin versions
Hi Wilhelm,
> following your suggestion, I finally managed to set up a Fiji update
> site ("ImagingBook") for our code.
That's great!
> Since ImageJ/Fiji is sensitive for identical plugin names, only one
> set should be installed at any time. Would you recommend to set up a
> separate update site for each collection or do you see any better
> solution?
If later editions of the book maintain backwards compatibility with older editions, you can have a single update site that simply ships the latest version of the plugins, and it should work with older editions of the book.
But it sounds like later editions are not backwards compatible, in which case multiple update sites are the recommended solution. E.g., you could have ImagingBook-1, ImagingBook-2, etc. numbered according to the editions.
As an example: I maintain an OMERO-5.0 update site with tools for connecting ImageJ to an OMERO 5.0.x server. But OMERO version 5.1.x is not backwards compatible, so there will need to be a separate OMERO-5.1 update site for it.
Alternately, if you have control over the Java package names, you can instead use a different package name for each edition. But since your book is already published in several editions and presumably includes code examples that all use the same Java package names, that solution would not work for you.
Regards,
Curtis
On Thu, Feb 5, 2015 at 10:43 AM, Burger Wilhelm <
[hidden email]<mailto:
[hidden email]>> wrote:
Hello Curtis,
following your suggestion, I finally managed to set up a Fiji update site ("ImagingBook") for our code.
Our installation provides alternative sets of plugins (i.e., jars for different book editions), which largely contain the same plugins (though in different Java packages) plus a single common library (located in /jars). Since ImageJ/Fiji is sensitive for identical plugin names, only one set should be installed at any time. Would you recommend to set up a separate update site for each collection or do you see any better solution?
Thanks much,
Wilhelm
> -----Original Message-----
> From: Burger Wilhelm
> Sent: Friday, December 05, 2014 10:46 PM
> To:
[hidden email]<mailto:
[hidden email]>
> Cc: Burger Wilhelm
> Subject: RE: Hough transform problem Edge detection
>
> Hello Curtis,
>
> yes I did. Our source code is currently undergoing major restructuring and
> migration. I have not used the Updater so far - is it also available in vanilla
> ImageJ or do I need to run Fiji? Is there any support for SVN?
>
> Thanks much,
> Wilhelm
>
> ________________________________________
> From: ImageJ Interest Group [
[hidden email]<mailto:
[hidden email]>] On Behalf Of Curtis
> Rueden [
[hidden email]<mailto:
[hidden email]>]
> Sent: Friday, December 05, 2014 22:17
> To:
[hidden email]<mailto:
[hidden email]>
> Subject: Re: Hough transform problem Edge detection
>
> Hi Wilhelm,
>
> > thanks for mentioning our "fabulous" collection
>
> Have you considered making an ImageJ update site?
>
http://imagej.net/Update_Sites>
> It would make installation easier for users.
>
> Regards,
> Curtis
>
ist:
http://imagej.nih.gov/ij/list.html--
ImageJ mailing list:
http://imagej.nih.gov/ij/list.html