Well, file permission/access is indeed something to keep in mind.
E.g. virusscanner are known to block access to a file for a short moment.
IDEs can also cause issues. If some file/code changes causes background
rebuild and you're doing an explicit Maven build yourself at the same
time, you could have an issue.
IIUC the failing project isn't always failing. This could be an
explanation.
Robert
On Fri, 28 Jul 2017 10:52:50 +0200, Dawid Weiss <dawid.we...@gmail.com>
wrote:
Have you double checked file permissions? if it can't read the parent
pom (maybe not all dirs are +x etc) then it wil have the behavior you
see
Come on, guys. :) I wouldn't ask if I didn't try it in many multiple
combinations. It is a heisenbug, but the reason for it is not a
trivial mistake on my part -- again: it fails on multiple (Windows)
machines; and it fails or not on the same machine, depending on the
path.
Weird, sure, but the more interesting.
I'll do some digging to see what this is, but pointers to code where I
could inject some debugging statements would be very welcome.
D.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
