[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Jindent

From: Zanabria, Moises
Subject: RE: Jindent
Date: Tue, 21 Jun 2005 14:54:10 -0500

Hi Tood,
Make sense to me, I think is better to run a "style checker" as a part
of the commitinfo which prevents a checkin if a particular source file
does have the xml style. 

Thanks for the tip.

-----Original Message-----
From: Todd Denniston [mailto:address@hidden 
Sent: Friday, June 17, 2005 4:49 PM
To: Zanabria, Moises
Cc: address@hidden
Subject: Re: Jindent

"Zanabria, Moises" wrote:
> Hi guys,
> I'm planning to run Our Java beautifier for the java files prior to
> committing, for that I need to run the Jindent, I know this could be
> done in the commitinfo file but I'm wondering if someone has been
> experienced this before and compare other thought.
> Thanks for any help.
> Moises.

One thing to keep in mind, if you run the beautifier from within the
commitinfo, only do so to test if the user did it, DO NOT put the output
the commitinfo beautifier into the repository.

Reason: there are situations where the user's sand box no longer
what is in CM when commitinfo beautifier data is put in the repository.
can lead to big confusion later on.

So the commitinfo beautifier output should only be used as an input to
if diff indicates the files (the input file to beautifier and the output
file from beautifier) given to it are different you exit with a non zero
value and remind the user to run the beautifier.

If the beautifier does not produce consistent output, stop using it.

Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane) 
Harnessing the Power of Technology for the Warfighter

reply via email to

[Prev in Thread] Current Thread [Next in Thread]