Thread: [jgrapht-developers] jalopy
Brought to you by:
barak_naveh,
perfecthash
From: Michael B. <beh...@in...> - 2004-09-20 12:18:12
|
-----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----- |
From: John V. S. <js...@ya...> - 2004-09-21 01:36:07
|
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 > |
From: Barak N. <ba...@3p...> - 2004-09-22 23:58:38
|
jalopy has a problem that it sometimes alternates between two formattings= . that is unfortunate because it creates "artificial changes" in unchanged files= . however, i'm not aware of a better free alternative to jalopy. Eclips' so= urce formatter is getting better, but is not there yet.=20 i suggest running jalopy on individual files rather than globally on all = source files. then to pick one of the two alternative that you like best and che= ck it in. If the file already in CVS, try to minimize the number of changes -- = to stay consistent to the formatting of previous version. i know it's not a great "solution", but have found it a reasonable way to= use jalopy, and take advantage of it's benefits. barak Quoting "John V. Sichi" <js...@ya...>: > It seems to be unpredictable, or maybe it's based on what it thinks has= =20 > changed after a cvs update. Kind of annoying. >=20 > The current approach is to make individual developers responsible for=20 > running jalopy on each checkin. An alternative would be to defer it,=20 > and make Barak responsible for running it as the first step in preparin= g=20 > a release. So the latest code in CVS would typically contain a mixture= =20 > of styles, but the released code would always be uniform. >=20 > JVS >=20 > Michael Behrisch wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > >=20 > > 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? > >=20 > > Michael > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1.2.4 (GNU/Linux) > >=20 > > iD8DBQFBTsqAZDyR4hR8HnQRAlQUAJ9g2WMvl2Oi04s6Kwxauow72O2BswCg0nhm > > aHpBz6gmlqu1y1NTUfHUfMk=3D > > =3Dol+S > > -----END PGP SIGNATURE----- > >=20 > >=20 > > ------------------------------------------------------- > > 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 > >=20 >=20 >=20 >=20 >=20 > ------------------------------------------------------- > 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 >=20 |
From: Barak N. <ba...@3p...> - 2004-09-22 23:58:42
|
jalopy has a problem that it sometimes alternates between two formattings= . that is unfortunate because it creates "artificial changes" in unchanged files= . however, i'm not aware of a better free alternative to jalopy. Eclips' so= urce formatter is getting better, but is not there yet.=20 i suggest running jalopy on individual files rather than globally on all = source files. then to pick one of the two alternative that you like best and che= ck it in. If the file already in CVS, try to minimize the number of changes -- = to stay consistent to the formatting of previous version. i know it's not a great "solution", but have found it a reasonable way to= use jalopy, and take advantage of it's benefits. barak Quoting "John V. Sichi" <js...@ya...>: > It seems to be unpredictable, or maybe it's based on what it thinks has= =20 > changed after a cvs update. Kind of annoying. >=20 > The current approach is to make individual developers responsible for=20 > running jalopy on each checkin. An alternative would be to defer it,=20 > and make Barak responsible for running it as the first step in preparin= g=20 > a release. So the latest code in CVS would typically contain a mixture= =20 > of styles, but the released code would always be uniform. >=20 > JVS >=20 > Michael Behrisch wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > >=20 > > 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? > >=20 > > Michael > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1.2.4 (GNU/Linux) > >=20 > > iD8DBQFBTsqAZDyR4hR8HnQRAlQUAJ9g2WMvl2Oi04s6Kwxauow72O2BswCg0nhm > > aHpBz6gmlqu1y1NTUfHUfMk=3D > > =3Dol+S > > -----END PGP SIGNATURE----- > >=20 > >=20 > > ------------------------------------------------------- > > 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 > >=20 >=20 >=20 >=20 >=20 > ------------------------------------------------------- > 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 >=20 |