Ok here's an update to this rule… It seems that the new way cannot be used to easily specify a group of files to fully exclude since it always checks the differenceType value (and it cannot be a wildcard).
So the new strategy should be: * In general always use the fine-grained way (i.e. <difference>) * When classes are moved to a new module or retired then use the "old" way (i.e. <exclude>) Thanks -Vincent On Oct 19, 2012, at 10:24 AM, Vincent Massol <[email protected]> wrote: > Hi guys, > > I've committed http://jira.xwiki.org/browse/XCOMMONS-283 which allows us to > very precisely exclude CLIRR violations. > > See > http://mojo.codehaus.org/clirr-maven-plugin/examples/ignored-differences.html > for details. > > For example I've just added an IRCBot exclude using this with: > > <ignored> > <difference> > <className>org/xwiki/ircbot/IRCBot</className> > <method>void initialize(java.lang.String)</method> > <differenceType>7012</differenceType> > <justification>IRCBot is still a young API. Added a new > initialize() method to support installing the > IRC Bot application in a subwiki</justification> > </difference> > </ignored> > > Now could every one who's added a clirr exclude please convert to the new way? > > This allows us to have fine-grained excludes and not exclude the whole file. > > Thanks > -Vincent > _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
