Very witty, but ... I've just spent a couple of quality hours with the MCOVERTURA bug list. I've found a few things that were already fixed but not marked as such, a couple of things that were fixed or mooted by recent changes, and a couple of things that combined great age, unclarity, and a lack of a repro. I closed all of them.
Remaining: A complex debate about running tests more than once. I suspect that no one has the stomach to change the behavior, and I'm not even sure that the behavior should be changed. An issue with surefire configuration that will probably be deemed not 'fixable' -- there's no maven mechanism I can see for injecting dynamic properties into a parallel lifecycle. An issue with release:perform that I just don't believe, but I've invited the OP to show me a (non)working example. A curious issue with surefire forkMode that I've sent mail about. Various things where the submitter hasn't done the diagnosis to see if the problem is with Cobertura *tout court* or with the plugin. Given the small group interested here, I'm in favor of setting a high repro bar for bug reports here. If the there isn't a complete failing case, and the problem does not leap out instantly, I'm in favor of closing (after inviting the OP to provide a repro). Now, I'm certainly not in charge here, so if everyone else things we should retain these JIRAs, I won't close them. (The ones I closed had particular reasons to justify the decision). On Sat, Apr 23, 2011 at 1:51 PM, Stephen Connolly <[email protected]> wrote: > x is the unknown quantity > spurt is a drip under pressure > > and that is the definition of an expert > > - Stephen > > --- > Sent from my Android phone, so random spelling mistakes, random nonsense > words and other nonsense are a direct result of using swype to type on the > screen > > On 23 Apr 2011 16:53, "Benson Margulies" <[email protected]> wrote: >> Hmm. >> >> Well, one issue here is that I'm not much of a Cobertura expert. I got >> into this because coworkers were bemoaning the lack of aggregation. >> Some of them there bug reports require a level of Cobertura knowledge >> that I just don't have. >> >> I'll revisit the list and see what else I can put a dent into. >> >> --benson >> >> >> On Fri, Apr 22, 2011 at 1:28 PM, Robert Scholte <[email protected]> >> wrote: >>> Some folks will say: release early, release often. >>> I agree, unless it's too often and too early. >>> Don't panic with the first issue of your release. Give users some time to >>> come with new issues. >>> Personnaly I just don't like to release for every little thingy. Here >>> it's >>> only one non-blocker while there are 39 open issues. >>> I'd say: try to pick up some more issues. >>> That's just my opinion. >>> >>> -Robert >>> >>>> Date: Fri, 22 Apr 2011 13:11:10 -0400 >>>> From: [email protected] >>>> To: [email protected] >>>> Subject: Re: [mojo-dev] propose cobertura-maven-plugin 2.5.1 to fix >>>> MCOBERTURA-145 >>>> >>>> Robert, >>>> >>>> I understand your point. At the same time, another spin around the >>>> crank (once I've got the fix and some tests) would take me about an >>>> hour, it would clean up the snafu with the JIRA report, and it would >>>> finish delivering the aggregation support, which was sort of the idea >>>> that got me started. What's the downside? >>>> >>>> --benson >>>> >>>> >>>> >>>> On Fri, Apr 22, 2011 at 11:58 AM, Robert Scholte >>>> <[email protected]> >>>> wrote: >>>> > I don't see the need to rush. It's not a blocker, just a major bug. >>>> > Regression happens. Just make sure that there's a good IT to fix and >>>> > verify >>>> > this issue. >>>> > >>>> > -Robert >>>> > >>>> >> Date: Fri, 22 Apr 2011 10:12:10 -0400 >>>> >> From: [email protected] >>>> >> To: [email protected] >>>> >> Subject: [mojo-dev] propose cobertura-maven-plugin 2.5.1 to fix >>>> >> MCOBERTURA-145 >>>> >> >>>> >> MCOBERTURA-145 seems to me to justify a turn of the crank, but not a >>>> >> move to 2.6. Anyone object? >>>> >> >>>> >> --------------------------------------------------------------------- >>>> >> To unsubscribe from this list, please visit: >>>> >> >>>> >> http://xircles.codehaus.org/manage_email >>>> >> >>>> >> >>>> > >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe from this list, please visit: >>>> >>>> http://xircles.codehaus.org/manage_email >>>> >>>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
