Hi Van,
>... then go for it! (and report back to the list on how it works). This all looks good to me! I had already used it. And it's a trick lighter to set up. So I report back to you with a description on how it works (setting-up, configure, run...). > we would get a very long list to go through ;-) Yep, but in any case, we can always play on the level of standard checks :-). Regards, - Nazir ________________________________ De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Van Mittal-Henkle Envoyé : mardi 18 décembre 2007 02:29 À : Developer Objet : Re: [Mifos-developer] Developer questionsrelatedtomifos application(build issues) Hi Nazir, Checkstyle looks like an interesting tool, but I'm not sure we're quite ready for something like that at this point unless we used it in a fairly limited way. Let's see if we can get our test case names refactored first. In the meantime, if you would like to experiment with Checkstyle to see if it could enforce the test case naming convention, then go for it! (and report back to the list on how it works). I suspect that if we ran the full style check, we would get a very long list to go through ;-) Cheers, --Van ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nazir LAJDEL Sent: Sunday, December 16, 2007 11:04 PM To: Developer Subject: Re: [Mifos-developer] Developer questions relatedtomifos application(build issues) Hi Van, >But no matter how the test runs are organized, I would still be in favor of >using a naming convention for the sake of consistency. >I'll put forward the suggestion of following the convention <classname>Test >for test class names. This convention should make code completion more >convenient than Test<classname>. So the proposal is >that when someone writes >the class MyClass then they would write MyClassTest to go along with it.. >If anyone else in the community has comments one way or another regarding >this, please chime in. After others have had a chance to comment, then if >we're in agreement, we can put this on our list of refactoring >to do. I suggest setting up a development tool to help programmers write Java code that adheres to a coding standard.We can automate the process of checking Java code to spare humans of this boring (but important) task. For example; "Checkstyle" can check many aspects of your source code. It's highly configurable and can be made to support almost any coding standard. Thoughts? - Nazir
------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
