22 Oct
2012
22 Oct
'12
9:23 a.m.
On Oct 22, 2012, at 9:20 AM, Vincent Massol <vincent(a)massol.net> wrote:
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).
For those interested in the code that checks the difference, it's in the match()
method of:
http://svn.codehaus.org/mojo/tags/clirr-maven-plugin-2.5/src/main/java/org/…
Thanks
-Vincent
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 <vincent(a)massol.net> 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.ht… 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