Hi, You mean with the new setup the build will fail because of a checkstyle issue? I personally find really hard for a "style" problem. (i.e something not related to a real technical problem).
On 11 October 2014 18:00, Hervé BOUTEMY <herve.bout...@free.fr> wrote: >> Log: >> - Fixed several Checkstyle errors. >> > notice that these are errors *reported by* Checkstyle, not really Checkstyle > errors > > Checkstyle should add "don't shoot the messenger" disclaimer ;) > > > I report here because next maven-parent version will enable Checkstyle check > on every build: we must all know that we chose the rules that Checkstyle will > report to us. If some rules are too strict, perhaps we'll need to relax them, > but be prepared to avoid blaming Checkstyle :) > > > Notice I prepared some escape ways when checkstyle:check will be run on each > build, to limit frustration: > > 1. verify phase only, to let us concentrate on making code work before fixing > broken coding conventions > > 2. @SuppressWarning support (MCHECKSTYLE-241) to ignore individual rules > directly into source code > > 3. CHECKSTYLE_OFF/ON support (MCHECKSTYLE-247) to ignore rules on complete > code fragments when necessary > > 4. fine grained global rule or even rule category (MCHECKSTYLE-242) to ignore > rules or rule categories of a whole build with a single property in pom.xml > > > I hope everybody will enjoy maven-parent 25 like me... > > Regards, > > Hervé > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
