http://imagej.273.s1.nabble.com/startup-plugins-from-more-than-one-folder-on-the-menu-tp5005223p5005302.html
> Whoa. Yep, that is definitely at least one bug. Darn.
> Hi Curtis,
>
> On Fri, 18 Oct 2013, Curtis Rueden wrote:
>
> > > In Fiji (actually, ImageJ2's legacy layer), we also added support for
> > > $HOME/.plugins/
> > ...
> > > If you do not like that location, you can override it by setting the
> > > system property ij1.plugin.dirs
> >
> > Thanks for the reminder! To document all this, I created a new page on
> the
> > wiki:
> >
> >
http://fiji.sc/Plugins>
> Thanks!
>
> > Unfortunately, I had some trouble getting the .plugins folder and the
> > ij1.plugins.dir system property override to work properly on my OS X
> > system:
> >
> > - When I put a plugin in $HOME/.plugins and launched Fiji, it was not
> > discovered.
> >
> > - The following command run from $HOME still did not find the plugin:
> > $FIJI/Contents/MacOS/ImageJ-macosx -Dij1.plugin.dirs=$HOME/.plugins
> >
> > - The same command run from $HOME/.plugins *did* find it, but did not
> find
> > the system plugins anymore.
> >
> > - So then I tried the following, also from $HOME/.plugins, and it worked:
> > $FIJI/Contents/MacOS/ImageJ-macosx
> > -Dij1.plugin.dirs=$FIJI/jars:$FIJI/plugins:$HOME/.plugins
> >
> > But the fact that the invocation is sensitive to your CWD seems like a
> bug
> > to me. Agreed?
>
> Whoa. Yep, that is definitely at least one bug. Darn. I thought that the
> unit test I wrote specifically to test this would make sure that it works.
>
> I will spend some time on Monday to debug this.
>
> Ciao,
> Dscho
>