I suggested before having the code
automatically formatted when a checkin or
checkout happens.
This could be done in 2 places:
1) The Jakarta script that
checks to see if a user has access to one of
the Jakarta projects.
2)CVS provides hooks/calls to be made
before or after any check out, or checkin operations.
The wrapper could look for the existance of
${Project}/conf/format.dat
where Project = jakarta-struts in our case
and if the 'format.dat' file exists automatically format the
code if it is a .java, .xml, or .xslt file.
Formatting on both checkin & checkout has the
advantage when doing a CVS diff between
an earlier version if struts code that wasn't formatted,
and a current version that is formatted.
In both cases both versions are in the same format.
Also if we change the formatting over time, all
previous versions would presented in the most current version.
-Rob
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
