Update:
I was able to fix the issue by renaming the problem folder/job from
"C:\Jenkins\workspace\Common presentation - DEV" to
"C:\Jenkins\workspace\Common *P*resentation - DEV"
If any can demystify this for me, that would be greatly appreciated...
Cheers,
Bert
On Tuesday, 9 April 2013
Hi,
Thanks for your quick reply, but I considered the spaces in the path and
job name though.
That doesn't seem to be the issue since the exact same project (and folder)
built on a different location (e.g. C:\Jenkins\workspaze) works just fine,
while building on the default location (C:\Jenkins
spaces in the path (caused by spaces in the job name)?
This is known to cause issues with some flaky maven mojos (although not
used flexmojos...) and would be worthwhile ruling out.
Writing configuration dump to C:\Jenkins\workspace\Common presentation -
DEV\target\common-presentation-4.3-SNAPSH
