Hi all, As you might have noticed, we recently made quite an effort in completing the Javadoc of the main magnolia project, in the 4.3 branch; as a tool to help this improve and not regress in the future, we've setup a few Checkstyle rules. (see BUILD-34 in Jira)
Now that this has been merged into the 4.4 branch and the trunk, we've enabled those rules; the build will break if new classes are introduced with Javadoc. This is applicable for any project that uses our parent poms, v17 or higher. Now, some of our modules aren't exactly up-to-date in that regard; here's how we will proceed: if you need to update the parent pom of a project (please do), ideally, you will update the javadoc, and all will be well. If for whatever reason, you can't do so: * do not disable checkstyle via the pom.xml * ping me, I will configure the Hudson job to *not* fail on violations. * by checking http://hudson.magnolia-cms.com/view/Checkstyle/ regularly, we can see where improvements need to be made. I will now go and configure each of our jobs to appear in this view, and ideally, we'll soon have loads of little zeroes popping up in that table. Cheers, -greg ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
