so that's how it works :) ... good to clear that up ... I'll just put the javadocs directory on cvsignore.
Marin� > -----Original Message----- > From: Nathan Bubna [mailto:[EMAIL PROTECTED] > Sent: 12. mars 2004 17:16 > To: Velocity Developers List > Subject: Re: cvs commit: > jakarta-velocity-tools/docs/javadoc/org/apache/velocity/tools/ > struts ValidatorUtils.html > > > Nathan Bubna said: > > Marin� A. J�nsson said: > > > Sorry, I haven't touched Nathan's patch ... and there > were no manual > > > javadoc fixes ... the javadoc commits in the HEAD were > because they > > > were all marked as 1.1 RC1. > > > > sorry, i still don't get it. javadocs are generated. if there's > > javadoc changes, then some source/control file must have > changed, and > > i didn't see where. did i just miss it? > > ah. i get it now. *i* changed the control file when i > changed the build.xml from 1.1-rc1 to 1.1-dev. :) the catch > is that actually we don't really need/want the subsequent > change in the javadocs to be committed. the committed > javadocs are really for the sake of the public website on > jakarta.apache.org. it's really the only reason we have them > checked in. and since we want the javadoc on the website to > match the most recent release (rather than the nightly > builds), we really only need/want to commit javadoc changes > when we do a release. still, as long as we haven't updated > the public site from CVS (and i presume you haven't), we > should be fine. no harm done. > > Nathan Bubna > [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
