I had same experience as Stephen; though I did get it to work at one point in m1 by setting build properties and some googling and hocus pocus to get the right clirr plugin jar installed. Sorry, but I just lost the drive where I had that all set up, so can't provide details atm.
In any case, I agree that we should in general run both jdiff and clirr reports prior to .x releases for commons components. These can be run from ant or the command line if necessary. I am not sure if the m2 plugins for exist yet, but we should include how-to for this in the revision of the release instructions for m2. Phil On 1/14/06, Stephen Colebourne <[EMAIL PROTECTED]> wrote: > I think I had to use ant to run it last as the maven plugin didn't work > for me. YMMV > > Stephen > > > Torsten Curdt wrote: > > Guys, > > > > anyone using clirr through maven? I would like to have > > it done (be)for(e) the BCEL release. But it would probably > > also make sense for the commons projects. > > > > cheers > > -- > > Torsten > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
