Open ops4j-issues opened 13 years ago
Harald Wellmann commented
Well, if you change the system property java.io.tmpdir
from the default to something else, then it's your own responsibility to ensure that 1) this path exists, 2) is a directory and 3) is writable.
I guess most Java applications will hiccup when you set java.io.tmpdir
to Nirvana...
Bram de Kruijff commented
I'm agnostic so can't say if $
{basedir}
/target/tmpdir qualifies as Nirvana. It is however a valid path on my filesystem where the java process is authorized to mkdir. IMHO any program should check, try to recover and eventually fail gracefully.
It's no biggy but AFAIK pax exam did before because I only ran into this after the upgrade. That's why i reported it as a minor bug. Change it into on improvement if you like :smile:
Harald Wellmann commented
Well, my assumption is that $
{basedir}
/target/tmpdir does not exist when you run mvn clean install, unless you have some action in your build before Surefire and Exam are running which creates it. Could you please check?
And I'm not aware of any changes between 2.2.0 and 2.3.0.M1 in that area - which of course doesn't mean that there aren't any :wink:
Bram de Kruijff created PAXEXAM-294
In a maven build I typically set the java.io.tmpdir to $
{basedir}
/target/tmpdir. Upgrading to 2.3.0.M1 this no longer works as it fails on the fact that the dir does not exist. I'd like to try and create it instead of trying 100000 times to inevitably fail :smile:
Affects: 2.3.0.M1 Votes: 0, Watches: 0