[mojo-dev] [jira] (MCLIRR-48) Add support for ignoring field or method breaking backward compatibility

[Lukas Krejci (JIRA)]

Lukas Krejci commented on MCLIRR-48 Add support for ignoring field or method breaking backward compatibility I see. So you'd exclude the results in the maven plugin, not directly inside Clirr. What I see as a difficulty with that approach is this. Consider your API evolving this way: int method() -> long method() at this point, you set up your maven plugin to ignore this difference by saying, for example, that you ignore return type changes on a this method, but then: long method() -> MyClass method() This is a substantial change that Clirr would NOT report, because it would exclude "return type change on method()", which at this point I think would be incorrect. So what I was looking for was to exclude specifically "int method() -> long method()" from being reported, every other change would still be reported. I see this ability lacking inside Clirr itself, because it doesn't report "both sides" of the difference.

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email