What if we want to automate the build of the javadoc? Can we just publish them to the website through ant using scp? I'd hate to lose the automated publishing of the javadoc.
Perhaps I could publish to my home directory using ant and then have a cron script on minotaur that cleans out the javadoc periodcially and copies the new ones from my home dir. I'm open to ideas here. BTW it turns out the javadoc differences were not due to timestamps but due to a different version of the JDK on the build machine. sean Sorry for adding to your email avalanche Craig :-( On 5/27/05, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > sound reasonable to me, to store JavaDoc not inside of SVN. > > .Matthias > > On 5/27/05, Craig McClanahan <[EMAIL PROTECTED]> wrote: > > On 5/25/05, Sean Schofield <[EMAIL PROTECTED]> wrote: > > > I just reran the build script (for the website) on a new build > > > machine. Evidently we ran into a timestamp issue again. The good > > > news is that the website build should be automated and if we only > > > build it on my machine we won't have all those extra commits. > > > > You also wouldn't have those commits if the javadoc files in question > > were simply installed on a standard web server somewhere and then > > pointed at by the website, rather than being part of the website build > > process. > > > > I've become convinced (and this last email flood, on top of a week's > > worth of other mail that just made it worse, reinforces this feeling) > > that committing Struts 1.0 javadocs to our source repository was a > > mistake. I would encourage the MyFaces folks to reconsider this as > > well. > > > > Craig > > > > > -- > Matthias Wessendorf >
