⚠	NOTICE! This is a static HTML version of a legacy ImageJ Trac ticket. The ImageJ project now uses GitHub Issues for issue tracking. Please file all new issues there.

Ticket #2033 (new defect)

Opened 2013-12-04T11:51:02-06:00

Last modified 2013-12-04T14:44:20-06:00

Find base directory gives wrong result

Reported by:	hinerm	Owned by:	curtis
Priority:	critical	Milestone:
Component:	Core	Version:	2.0.0-beta-7
Severity:	critical	Keywords:
Cc:	curtis	Blocked By:
Blocking:

Description

If ImageJ.app lives in a subfolder where the parent has a pom.xml, the wrong directory can be returned as the base directory.

An easy way to see this is to use bin/populate-app.sh to create an IJ2 installation in a subdirectory (e.g. /imagej/app). Run this IJ2 app and execute "Edit>Options>Memory & Threads", then set the memory to a value of your choice. The output ImageJ.cfg will be placed in the /imagej directory, instead of /imagej/app/ImageJ.app/.

Change History

comment:1 Changed 2013-12-04T14:43:16-06:00 by curtis

I am unable to duplicate this bug on my system.

comment:2 Changed 2013-12-04T14:44:20-06:00 by curtis

Can you please run the System Information command on an affected launch and see what the value of system property ij.dir is? The launcher is supposed to set it, and the getBaseDirectory() method uses it, if available, to decide the base directory. This logic works as expected on my system.