I see, this explains why you where talking about doing a big CVS commit.. The site documentation is all in CVS in the Maven generated format.
yep.
Therefore, when I make a change, and rerun the site docs, those changes in the site docs caused by my change are then committed to CVS, and then this job just pulls it out... Correct?
yep.
I was thinking that you had some sort of Cruisecontrol type app where it was pulling stuff out of cvs, running the site, and then uploading it...
we had: forrestbot. Since we're no longer using forrest, that's no longer an option.
Such a script would be simple enough as well. I'm sure some people have maven-based autopublishing set up.
- LSD
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
