Back in January, the JMeter committers agreed to use the Jakarta-Turbine conventions for code formatting (http://jakarta.apache.org/turbine/common/code-standards.html). Not my personal favorite, but I'm not picky as long as there is some kind of convention. If you've been watching my commits over the past couple of months, you'll have noticed I've been working on making the existing JMeter code conform to this standard. This probably could have been done with an automated tool, but I used it as an opportunity to become more familiar with the code. I'm not quite done yet -- JOrphan is not yet done. And I've really focused mainly on line length, no use of tabs, and curly brace placement, so there are probably other conventions that aren't being followed.
So, now that most of the code actually follows the convention, let's try to stick to it with new code as well. For those of you who use Eclipse, I added some information to the Wiki (from the main JMeter Wiki page choose JMeterDevelopment and find the link under "Tools") describing some settings which work well. If you work on multiple projects you might consider using a separate Eclipse workspace for JMeter so that you can have different settings than you might use on other projects.
Please feel free to update the Wiki with additional suggestions. I might add some information about using the Checkstyle Eclipse plugin to catch any incorrect formatting.
Jeremy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
