On Aug 13, 2009, at 12:30 PM, Hans Dockter wrote:
On Aug 1, 2009, at 12:13 AM, Adam Murdoch wrote:
Steve Appling wrote:
I had my first encounter with the new checkstyle tasks as part of
making an explodedDist of gradle today. I love having support for
this, but have a couple of thoughts.
BTW, I' want to gradually switch on more checks for the Gradle
build. Does anyone have any favourite checks they want to see
switched on? Hated checks they don't want?
For me the most important check at the moment is javadoc for public
API methods. I have implemented this check and it gives us a lot of
output. I have of course excluded the internal packages. A lot of
the warnings are simply missing API docs. A large other chuck might
point out that some classes do not belong in public packages.
I have submitted the Javadoc check to VCS. But it is commented out in
the checkstyle.xml. But we can uncomment it for local builds to see
where we need to add javadoc. I think we should have a running javadoc
check before the 0.8 release.
Other check I would like are: EmptyBlocks, NeedBraces, Headers
I have added Header checks.
- Hans
--
Hans Dockter
Gradle Project Manager
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
