The reasons for this are primarily historical at this point. I
believe the original motivation was to make it easy to update the
public site by just doing svn update.
At this point, i guess i'm +0.1 on removing the generated
documentation from version control in this version. Once we have
velocity.apache.org up and a totally different way of building the
site, then i'll be +1.
On 12/22/06, Henning P. Schmiedehausen <[EMAIL PROTECTED]> wrote:
Hi,
I noticed that the Javadocs and docs output are checked into
SVN. Besides from giving me a big number of M(odified) files from SVN
when I do svn status after building the tools, do we need that?
We do build these files with a regular build anyway and people actually
getting the source code from SVN probably know their way around enough to
build these themselves.
I'm +1 for removing the generated files from SVN.
Best regards
Henning
--
Henning P. Schmiedehausen -- [EMAIL PROTECTED] | J2EE, Linux,
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person
Open Source Consulting, Development, Design | Velocity - Turbine guy
"Save the cheerleader. Save the world."
---------------------------------------------------------------------
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]
