Posted by
Burger Wilhelm on
Mar 28, 2015; 12:29pm
URL: http://imagej.273.s1.nabble.com/Update-site-with-multiple-plugin-versions-tp5011460p5012227.html
Hello Curtis,
I seem to be too stupid to use Fiji update sites properly...
I have locally modified jar files that I want to upload to my update site(s). However (with Fiji updated, using the ImageJ updater in Advanced Mode and after reading the instructions over and over) right-clicking on the local file gives me only these options:
- Keep as-is,
- Update,
- Uninstall.
No 'Upload to My Site' option anywhere (unlike described in the wiki). How do I re-connect to 'my sites', anywhere to register/log in again?
Thanks for any hints...
--Wilhelm
________________________________
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
--
ImageJ mailing list:
http://imagej.nih.gov/ij/list.html