http://imagej.273.s1.nabble.com/Update-site-with-multiple-plugin-versions-tp5011460p5012373.html
difficulties. Otherwise, if everyone waits for the software to become
> Hello Birgit,
>
> thanks for the advice -- this is what Curtis had also suggested. However,
> I tried these steps several times but the option to upload to an update
> site never shows (Win7 with Java 8, 64 bits). After spending hours on this
> I will probably stay clear of update sites until the mechanism has matured.
>
> Thanks again!
> Wilhelm
>
> ________________________________________
> From: ImageJ Interest Group [
[hidden email]] On Behalf Of Birgit
> Möller [
[hidden email]]
> Sent: Sunday, March 29, 2015 10:51
> To:
[hidden email]
> Subject: Re: Update site with multiple plugin versions
>
> Hi Wilhelm,
> I observed the same problem of lacking an option to upload files to our
> update site when testing update sites. It seems that not the full set of
> available options is properly shown in the GUI of the updater upon
> start-up. When I changed the selection once, e.g., from 'Keep as-is' to
> 'Uninstall', suddenly an additional option to upload the files to our own
> update site appeared which I then could select. From my observations I
> would say that the updater lacks somewhere an explicit update of its GUI
> during start-up, i.e., it seems that first an interaction with the combobox
> is required to trigger an update event, and only then all options are
> properly shown.
> Regards,
>
> Birgit
>
> On Sat, 28 Mar 2015 14:03:09 +0100, Burger Wilhelm <
>
[hidden email]> wrote:
>
> >Thanks for the rapid help! But how do I "enter credentials" for my site
> in the Manage Update Sites?? I only see buttons for
> >- Add my site,
> >- Add,
> >- Remove,
> >- Close.
> >Right click on any of my sites in the list does nil. "View changes" does
> not show any files flagged for update. Am I missing something?
> >
> >--Wilhelm
> >
> >
> >________________________________
> >From:
[hidden email] [
[hidden email]] On Behalf Of
> Curtis Rueden [
[hidden email]]
> >Sent: Saturday, March 28, 2015 13:51
> >To: Burger Wilhelm
> >Cc: ImageJ Interest Group
> >Subject: RE: Update site with multiple plugin versions
> >
> >
> >Hi Wilhelm,
> >
> >First, make sure you have credentials entered for your site in the Manage
> Update Sites dialog.
> >
> >Then, make sure no files are flagged for update--the "View changes" mode
> is very useful for that. After marking any such files with "keep as is" the
> upload option should magically appear.
> >
> >I agree it is very unintuitive. Would you mind filing an issue on GitHub
> (imagej/imagej-updater repo) to improve the behavior?
> >
> >Thanks,
> >Curtis
> >
> >On Mar 28, 2015 7:29 AM, "Burger Wilhelm" <
[hidden email]
> <mailto:
[hidden email]>> wrote:
> >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]<mailto:
[hidden email]> [
>
[hidden email]<mailto:
[hidden email]>] On Behalf Of
> Curtis Rueden [
[hidden email]<mailto:
[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>
> --
> ImageJ mailing list:
http://imagej.nih.gov/ij/list.html> --
> ImageJ mailing list:
http://imagej.nih.gov/ij/list.html>