On 11/22/05, James Mitchell <[EMAIL PROTECTED]> wrote: > It's a good idea at least to give it a once over by hand and make sure > everything was built correctly....especially if there are doc changes that > might cripple the site output.
Whoever is editing files should be doing that. My read of the site plugin docs says that unless you configure it to 'clean', it won't remove files, it just adds and overwrites. And it may not even try the upload if the site build fails... I'll have to break one of the xdocs and see what happens. Bad content in otherwise well formed xml files will be caught when the commit message goes to the list, so... > If we wanted to automate this, we should at least provide ourselves a time > buffer to react to anything really bad. > > I suppose we could setup a weekly deployment from a staging site: IMO, a week is much too long. Back in the old days, the site used to get published nightly. I'm hoping that things get active enough around here that we'll need that again. ATM, I just want it. :) But I'm fine with publishing changes as needed, too -- especially now that it's a single command. Just having fun teaching Maven new tricks... -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
