When letting Jenkins run unit tests, it is very convenient to be able to inspect the temporary directories used for testing. This is not possible if the temporary directories are stashed away in /tmp/ (which Jenkins does not make visible, for obvious reasons). If, however, we store temporary directories into the target/ directory -- under a name that corresponds to the calling site -- it is much easier to debug.
This is exactly what we did e.g. in the ij1-patcher project: https://github.com/imagej/ij1-patcher/blob/11ff5ef823ac03aff0f77187c16e843b3aa25352/src/test/java/net/imagej/patcher/TestUtils.java#L65-L93
We should port this into scijava-common so that we do not copy-paste code all the time...
When letting Jenkins run unit tests, it is very convenient to be able to inspect the temporary directories used for testing. This is not possible if the temporary directories are stashed away in
/tmp/(which Jenkins does not make visible, for obvious reasons). If, however, we store temporary directories into thetarget/directory -- under a name that corresponds to the calling site -- it is much easier to debug.This is exactly what we did e.g. in the ij1-patcher project: https://github.com/imagej/ij1-patcher/blob/11ff5ef823ac03aff0f77187c16e843b3aa25352/src/test/java/net/imagej/patcher/TestUtils.java#L65-L93
We should port this into scijava-common so that we do not copy-paste code all the time...