11 Apr
2012
11 Apr
'12
6:46 a.m.
Hi devs,
I noticed that no CLIRR errors are generated for modules that have been
moved from platform to commons. This isn't good, since we're not
reporting all the API breakages.
I propose that whenever a module is moved, we add a special
configuration for the maven clirr plugin in that module's pom.xml file,
so that it compares with the previous version with the platform groupId.
See
http://mojo.codehaus.org/clirr-maven-plugin/examples/specific-artifacts.html
for more details about the required configuration.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/