Re: a small bug in the new launcher

[dscho]

Hi Jerome,

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.

For the future, please do not keep such reports secret: other people might
have the same problem, and in order to avoid wasting their time, it would
be good to have the record on the mailing list, also for people who might
Google for the same problem later. It is called "Open" Source for a reason
;-)

Thanks,
Johannes

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html

[dscho]

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

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html

[Jerome Mutterer-3]

Hi Johannes,
I just downloaded the new launcher version and it works now as expected.
Thanks a lot for fixing this.

Sincerely,

Jerome.

On 20 June 2013 22:36, Johannes Schindelin <[hidden email]>wrote:

> 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
>

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html

[dscho]

Hi Jerome,

On Thu, 20 Jun 2013, Jerome Mutterer wrote:

> I just downloaded the new launcher version and it works now as expected.
> Thanks a lot for fixing this.

You're welcome!

Thanks for reporting and testing!
Johannes

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html

We are having a similar problem. We want to use plugins directory on a mapped network drive but ImageJ is not able to see the plugins. We are using ImageJ on Windows 7 computers. I have tried a few things listed below:

- launching Imagej with switch -Dplugins.dir=H:\ImageJ
- adding -Dplugins.dir=H:\ImageJ to ImageJ.CFG file
- Installed new version of ImageJ, did not change in behaviour
- Copied plugins to Program Files\ImageJ\plugins\Custom and then it works (if the plugins are in a sub-folder e.g. \....\Plugins\Custom\Navneet then ImageJ won't see it either
- Tried a local folder with -Dplugins.dir folder, plugins still don't show up in plugins menu.

Any suggestions? Am I doing something wrong? I am not an ImageJ user. just trying to get it working in our lab.

Thanks,
Navneet

[Michael Schmid]

Hi Navneet,

without having tried it, my guess is that the plugins directory should be named 'plugins', and the default macros directory would reside in the same directory as 'plugins'.

You can get the place where ImageJ expects its plugins if you paste the following line with CTRL-SHIFT-V

  getDirectory("plugins");

and then type CTRL-R for "run macro".

You should also see what plugin directory ImageJ uses if you start ImageJ in debug mode (Add switch --debug to the arguments of the launcher).


So, if you start ImageJ with -Dplugins.dir=H:\ImageJ or -Dplugins.dir=H:\ImageJ\plugins
I would assume that the plugins should be in H:\ImageJ\plugins (in both cases), and macros in H:\ImageJ\macros.

ImageJ searches for plugins only in the plugins directory and its immediate subdirectories, not in any deeper levels. So you can't have plugins in ...imageJ\plugins\Custom\Navneet.


Michael
________________________________________________________________
On Jan 12, 2015, at 17:39, [hidden email] wrote:

> We are having a similar problem. We want to use plugins directory on a mapped
> network drive but ImageJ is not able to see the plugins. We are using ImageJ
> on Windows 7 computers. I have tried a few things listed below:
>
> - launching Imagej with switch -Dplugins.dir=H:\ImageJ
> - adding -Dplugins.dir=H:\ImageJ to ImageJ.CFG file
> - Installed new version of ImageJ, did not change in behaviour
> - Copied plugins to Program Files\ImageJ\plugins\Custom and then it works
> (if the plugins are in a sub-folder e.g. \....\Plugins\Custom\Navneet then
> ImageJ won't see it either
> - Tried a local folder with -Dplugins.dir folder, plugins still don't show
> up in plugins menu.
>
> Any suggestions? Am I doing something wrong? I am not an ImageJ user. just
> trying to get it working in our lab.
>
> Thanks,
> Navneet
>
>
>
> --
> View this message in context: http://imagej.1557.x6.nabble.com/Re-a-small-bug-in-the-new-launcher-tp5003541p5011186.html
> Sent from the ImageJ mailing list archive at Nabble.com.
>
> --
> ImageJ mailing list: http://imagej.nih.gov/ij/list.html

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html