As this is a multimodule component, report content tends to be more correct when relegated to the module level. Please see:
http://people.apache.org/~mbenson/commons-weaver-1.1-rc1/commons-weaver-processor/project-reports.html http://people.apache.org/~mbenson/commons-weaver-1.1-rc1/commons-weaver-modules-parent/commons-weaver-privilizer-parent/commons-weaver-privilizer-api/project-reports.html http://people.apache.org/~mbenson/commons-weaver-1.1-rc1/commons-weaver-modules-parent/commons-weaver-privilizer-parent/commons-weaver-privilizer/project-reports.html http://people.apache.org/~mbenson/commons-weaver-1.1-rc1/commons-weaver-modules-parent/commons-weaver-normalizer-parent/commons-weaver-normalizer/project-reports.html http://people.apache.org/~mbenson/commons-weaver-1.1-rc1/commons-weaver-maven-plugin/project-reports.html http://people.apache.org/~mbenson/commons-weaver-1.1-rc1/commons-weaver-antlib-parent/commons-weaver-antlib/project-reports.html * I'll go ahead and include these links in future VOTE emails for this and other multimodule components. *The clirr report has actually been suppressed (as far as possible) in the Antlib because the clirr-maven-plugin cannot handle dependencies in provided scope (namely, the Ant API) that are exposed in the public API. [weaver] 1.1 declares org.apache.ant:ant in compile scope, so we should be able to use clirr here going forward. Thanks for looking, Matt On Wed, Jun 4, 2014 at 4:12 PM, Emmanuel Bourg <ebo...@apache.org> wrote: > Le 04/06/2014 23:02, Gary Gregory a écrit : > > aaaaaalmost -1 because there is no Clirr report on the site so I cannot > > tell if 1.1 breaks or maintains BC. > > Commons Weaver 1.0 has been released 3 months ago, I don't think it > would be fair to block the release for a breaking change with such a > young component. > > Emmanuel Bourg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
