I don't think the list got this. -----Original Message----- From: Mike Perham Sent: Tuesday, January 31, 2006 2:47 PM To: 'dev@mojo.codehaus.org' Subject: RE: [mojo-dev] Release cobertura plugin
I'm -1 on releasing Cobertura until we fix MOJO-226 and MOJO-271. I have just submitted a patch to fix both but it is controversial and I would like a core M2 dev to review it before I am willing to commit it. Cobertura requires asm and a bunch of others to instrument but requires nothing to actually run the instrumented code during tests. So I cloned cobertura into a separate cobertura-runtime artifact and add that to the project classpath instead of the cobertura artifact itself. It's a hack but I don't know of any cleaner way to handle the situation. -----Original Message----- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 31, 2006 11:43 AM To: dev@mojo.codehaus.org Subject: Re: [mojo-dev] Release cobertura plugin I'm looking at it now. By lots of questions, they're all from the same user. The cobertura plugin has never been released. It doesn't have a JIRA component because its in the sandbox. The Mojo JIRA projects haven't been created yet, but Jason was collecting the data. - Brett Carlos Sanchez wrote: > Hi, > > There're problems with cobertura and 2.0.2, could somebody take care > of making a bugfix release to address at least that problem that is > causing compatibility problems? it's causing lots of questions in the > mailing list. > > BTW is it possible to create a JIRA project for each of the active > plugins so we can keep better track of releases? > > Regards >
