-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Hudson 1.355, Windows Server 2008
I am having the problem that Javadoc publishing fails after the first successful build. That is, build #1 succeeds and publishes Javadoc, but build #2 onwards fails with the following error:
ERROR: No javadoc found in C:\Program Files\Hudson\jobs\FLTools\workspace\docs/api/html: null
I found however that after deleting the published Javadoc directory, C:\Program Files\Hudson\jobs\FLTools\javadoc, the build succeeds again. Therefore, it looks like Hudson is having problems overwriting previously published Javadoc.
This will happen if the javadoc directory in your job's workspace is exactly the same as it was for the previous build (ie, there is nothing new to copy..). Does your job skip javadoc generation when it sees javadoc from a previous run? Can you do a "clean" build to force javadoc to run again?