Posted by
Jarek Sacha-2 on
URL: http://imagej.273.s1.nabble.com/JarUpdater-An-easy-way-to-distribute-plugin-updates-tp3685495p3685499.html
Johannes:
Fiji is much more than the updater; it is also a distribution of large
amount of plugins. What would be nice, is to separate the updater mechanism
from the other Fiji plugins. Something similar to the Update Centers
provided, for instance, by Eclipse and NetBeans. User could select which
update centers to use. Even better which plugin clusters to use. User could
control which types of plugins he/she is interested in. Having a standard
way to provide plugins, other projects that provide plugins (including the
main ImageJ website) could setup their update centers that would be
registered with ImageJ website.
I do appreciate the complexity of resolving dependencies and conflicts
between library versions, and creating update descriptions for the updater.
That is the reason why solution to this so appealing to many users of
ImageJ. Unless you are using Fiji with all of its plugins and only its
plugins, it has to be done manually.
Jarek
On Thu, Mar 3, 2011 at 8:15 PM, Johannes Schindelin <
[hidden email]> wrote:
> Hi Jarek,
>
> On Thu, 3 Mar 2011, Jarek Sacha wrote:
>
> > Johannes:
>
> please Cc: me when you address me directly, unless you _want_ me to miss
> your mail.
>
> > I am looking forward to a plugins updater that have the features you
> > mention and can run with or without Fiji. Updating plugins and their
> > dependencies is a pain right now. A flexible mechanism that works with
> > "plain" ImageJ and custom distributions is really needed.
>
> The whole point of Fiji is what you claim you want for "plain" ImageJ. I
> know what a pain dependencies are. That's why we started Fiji. Please
> understand that porting the facilities you asked for to ImageJ would
> accomplish nothing else than recreating Fiji.
>
> Hth,
> Johannes
>