One possible solution is that for the modified files that cause conflicts you apply jalopy before performing a CVS update. Is that applicable in your situation?
At 10:51 PM 4/5/2003 +0200, you wrote:
I just started to get this mailing list. So I cannot reply to the thread "Applying Jalopy?".
Is anyone applying Jalopy to log4j?
I would be happy if the source code is easier to read by someone who is used to the coding standards (checkstyle and I).
I think, it should be done by one person for the whole project at once on a certain day announced here. So everone can synchronize his work with CVS and the whole problem of conflicts because of reformatting will happen once and for all.
According to the standard, the indentation size should be 4 and not 2 as it is specified in the configuration.
Ceki, you already reformatted some classes (unfortunately some I was working on). Can you do the reformatting for log4j? Only the fileset "styled_files" must be extended for the task runJalopy.
I could do it too. But I don't have the "authority" to change all files.
Ingo
--
Ceki
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]