Hi Peter,
instead of
Arguments tab:
Program arguments: -Dplugins.dir=<full path to project dir>
-Dmacros.dir=<full path to project dir>
VM arguments: -Xms256m -Xmx512m
put the "Program arguments" into the "VM arguments" such as:
Arguments tab:
VM arguments:
-Xms256m
-Xmx512m
-Dplugins.dir=${workspace_loc:<project dir>}
-Dmacros.dir=${workspace_loc:<project dir>}
The Program arguments will not be interpreted by ImageJ.
Alternatively (and if you don't like your home-directory), you could set
the "Working directory" to ${workspace_loc:<project dir>}. ImageJ seems
to search there as well.
I wrote that to Kimo some weeks ago and he recognized it but seems to
have no time currently to fix it on the page. Now you have a solution.
Don't give up too early with eclipse---it's a really nice IDE ;)
Best regards,
Stephan
On Sun, 2008-10-12 at 16:24 -0300, Peter Gregson wrote:
> I read the blog by Mika Kimo Johnson on developing plugins in
> eclipse. It seems to work although I have a significant problem.
> When I run the plugin, eclipse invokes ImageJ, but it does it in a
> way
> that it doesn't see the the plugins that I need to have. My project
> requires a number of plugins to process the image stack prior to
> using
> the plugin that I am developing. If I cannot execute those plugins
> from the keyboard or via a script, then eclipse's ability to execute
> ImageJ from inside it is not helpful to me.
>
> I have a second problem as well. It appears that ImageJ 1.40m (the
> latest) has a feature under Help -> Update Menus to update the list
> of
> plugins. However, if the plugin itself is not updated if a
> previous
> version was already detected on a previous invocation of Help ->
> Update Menus or on startup of ImageJ
>
> These two problems make the development of complex image processing
> systems a very painful problem. Does anyone know a way around
> either
> of them?
>
> Best regards,
>
> Peter
> Peter Gregson, Ph.D., P.Eng.
> Professor, E&CE
Locked
