Hi, We can leave the jcoverage plugin as is, there's no need to remove it.
I suggested starting a new project in SF so this guys could easily work on it and later it could be added to the main distribution. If not, I may find the time to create a new plugin in apache but then apache comitters would need to make the patches, releases, etc. I'd like to see opinions on this, having tha plugin in a JIRA issue is not the best way. Regards Carlos On 6/7/05, J�rg Schaible <[EMAIL PROTECTED]> wrote: > Carlos, > > Carlos Sanchez wrote on Tuesday, June 07, 2005 7:36 PM: > > Hi, > > > > As I've commented in the JIRA issue the plugin can be hosted > > in SF http://maven-plugins.sourceforge.net/ and if everything > > goes ok it could be added to the maven distribution. > > What's the point in keeping jcoverage plugin then? JCoverage itself has > serveral problems and fixes did not get applied by the jcoverage team. That > was the main reason for the cobertura fork anyway. > > - J�rg > > --------------------------------------------------------------------- > 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]
