Re: [jgrapht-developers] jalopy

[John V. S. <js...@ya...>]

It seems to be unpredictable, or maybe it's based on what it thinks has 
changed after a cvs update.  Kind of annoying.

The current approach is to make individual developers responsible for 
running jalopy on each checkin.  An alternative would be to defer it, 
and make Barak responsible for running it as the first step in preparing 
a release.  So the latest code in CVS would typically contain a mixture 
of styles, but the released code would always be uniform.

JVS

Michael Behrisch wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> I just ran 'ant jalopy' and it modified all source files (although apparently
> according to the jalopy-settings in etc), but I dont think that this
> was intended, bacause a lot of files should already adhere to
> the jalopy standards, shouldn't they?. Did I do something wrong?
> 
> Michael
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
> 
> iD8DBQFBTsqAZDyR4hR8HnQRAlQUAJ9g2WMvl2Oi04s6Kwxauow72O2BswCg0nhm
> aHpBz6gmlqu1y1NTUfHUfMk=
> =ol+S
> -----END PGP SIGNATURE-----
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
> Project Admins to receive an Apple iPod Mini FREE for your judgement on
> who ports your project to Linux PPC the best. Sponsored by IBM.
> Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
> _______________________________________________
> jgrapht-developers mailing list
> jgr...@li...
> https://lists.sourceforge.net/lists/listinfo/jgrapht-developers
>