http://imagej.273.s1.nabble.com/Re-a-small-bug-in-the-new-launcher-tp5003541p5003548.html
> Hi Jerome,
>
> On Thu, 20 Jun 2013, Johannes Schindelin wrote:
>
> > On Thu, 20 Jun 2013, Jerome Mutterer wrote:
> >
> > > I think that the new launcher that is now shipped with the 1.47 windows
> > > installer disregards the -Dplugins.dir command line option.
> > >
> > > What I did to test this:
> > >
> > > - installed on windows from
> > >
http://jenkins.imagej.net/job/ImageJ1-releases/label=Windows/34/> > > - edited the ImageJ.cfg file to include -Dplugins.dir=C:\jerome
> > > - start ImageJ.exe : plugins are loaded from ImageJ folder.
> > >
> > > renaming ImageJ.exe to debug.exe produces the following output:
> > >
> > > Found Java options in ImageJ.cfg: '-Xmx768m -Dplugins.dir=C:\jerome
> ij.jar'
> > > JRE found in 'C:\DOCUME~1\ADMINI~1\Desktop\IMAGEJ~3/jre'
> > > javaw -Dplugins.dir=C:\\jerome ij.jar -Dpython.cachedir.skip=true
> > > -Dplugins.dir=
> > > C:\\DOCUME~1\\ADMINI~1\\Desktop\\IMAGEJ~3 -Xmx768m -Xincgc
> > > -XX:PermSize=128m .....
> > >
> > > Where you can see that the option is found in the cfg file, but passed
> > > *twice* to the javaw command. I suppose that the second default
> > > occurrence overwrites the correct first one.
> >
> > Thanks for reporting this. I will take care of it later today.
>
> And so I did. Please find the new version here:
>
>
>
http://jenkins.imagej.net/job/Windows-Fiji-launcher-with-icons/label=Windows/lastSuccessfulBuild/artifact/ImageJ1-win32.exe>
> (Assuming that you use Windows on a 32-bit Intel processor)
>
> Ciao,
> Johannes
>