Other people at Codehaus. There is some overlap, but I probably not for the
last couple of years.
On 31/03/2011, at 4:45 AM, Benson Margulies wrote:
> Dear Maven PMC,
>
> Is the maven-cobertura-plugin on Codehaus under the supervision and
> care of the Apache Maven PMC, or is
maven-cobertura-plugin is at Mojo: http://mojo.codehaus.org/
see FAQ for more information: http://mojo.codehaus.org/faq.html
Regards,
Hervé
Le mercredi 30 mars 2011, Benson Margulies a écrit :
> Dear Maven PMC,
>
> Is the maven-cobertura-plugin on Codehaus under the supervision and
Dear Maven PMC,
Is the maven-cobertura-plugin on Codehaus under the supervision and
care of the Apache Maven PMC, or is it just the product of some folks
who maintain it at codehaus?
--benson
-
To unsubscribe, e-mail: dev
Hello!
I've recently started looking into the Cobertura plugin as I need
couple features that are missing. Namely:
http://jira.codehaus.org/browse/MCOBERTURA-33
http://jira.codehaus.org/browse/MCOBERTURA-65
http://jira.codehaus.org/browse/MCOBERTURA-66
I'm going to explain now what I
I think it is clear now - Ralph, you jumped into a thread about the Maven 2
Cobertura plugin, and began asking about the Maven 1 plugin. This confused
subsequent replies!
If you have Cobertura questions or issues, please start a new thread as
Lukas suggested.
-Original Message-
From
I didn't talk abou lifecycle and phases and a surefire plugin. My first
response to this thread was to simply ask what the "well known problem"
was in the hopes I could figure out how to get the cobertura plugin for
maven 1 working better. (I did by the way). You must have co
maven.compile.debug setting?)
Cheers,
-Lukas
[1] http://maven-plugins.sourceforge.net/maven-cobertura-plugin/
Ralph Goers wrote:
No, we have many Maven 1 based projects. We have wanted to move to Maven
2 but cannot until MNG-1577 is applied. I've actually waded through
quite a bit of the code in
No, we have many Maven 1 based projects. We have wanted to move to Maven
2 but cannot until MNG-1577 is applied. I've actually waded through
quite a bit of the code in both versions.
Version 1.3 of the Cobertura plugin also uses Cobertura 1.8 so I guess
there must be something blat
dnesday, February 07, 2007 9:14 AM
> Subject: Re: Lifecycle issues with Cobertura plugin and custom plugin
>
>
>> What is this well known problem. I tried upgrading the plugin for maven
>> 1.0.2 from version 1.1.1 of cobertura to 1.3 and have the same problem -
>> a
>
To: "Maven Developers List"
Sent: Wednesday, February 07, 2007 9:14 AM
Subject: Re: Lifecycle issues with Cobertura plugin and custom plugin
What is this well known problem. I tried upgrading the plugin for maven
1.0.2 from version 1.1.1 of cobertura to 1.3 and have the same problem
of the plugin and see if that fixes it.
- Original Message - From: "drekka"
<[EMAIL PROTECTED]>
To:
Sent: Wednesday, February 07, 2007 1:13 AM
Subject: Lifecycle issues with Cobertura plugin and custom plugin
Hi guys,
I've been trying to nut this out for a c
Sounds like the well-known Cobertura 2.1 problem. Try explicitly specifying
version 2.0 of the plugin and see if that fixes it.
- Original Message -
From: "drekka" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, February 07, 2007 1:13 AM
Subject: Lifecycle issues with Cobe
;ve
setup the plugin within maven. From reading the source of the cobertura
plugin it appears that the plugin forks a new process to run the test phase
again. At this point I'm not sure what happens as the maven doco is really
hard to follow and leave me with more questions than answers. The lo
debug I can
see that the cobertura plugin jumps in and re-assigns the projects tart
class directory as follows:
Without cobertura: /target/classes
With cobertura: /generated-classes/cobertura
I cannot see any difference in the directories cobertura generates and my
class loader seems to think the
[ http://jira.codehaus.org/browse/MEV-321?page=all ]
Carlos Sanchez closed MEV-321:
--
Resolution: Fixed
It's already there
> Cobertura plugin requires a new "psuedo-artifact"
> -
[ http://jira.codehaus.org/browse/MEV-321?page=all ]
Mike Perham reopened MEV-321:
-
There is no cobertura-runtime artifact in
http://www.ibiblio.org/maven2/cobertura/ still...
> Cobertura plugin requires a new "psuedo-
[ http://jira.codehaus.org/browse/MEV-321?page=all ]
Carlos Sanchez closed MEV-321:
--
Assign To: Carlos Sanchez
Resolution: Fixed
Will be in the repo soon
> Cobertura plugin requires a new "psuedo-
.
> Cobertura plugin requires a new "psuedo-artifact"
> -
>
> Key: MEV-321
> URL: http://jira.codehaus.org/browse/MEV-321
> Project: Maven Evangelism
> Type: Bug
> Reporter: Mike Perham
&
tura
${project.version}
oro
oro
asm
asm
log4j
log4j
javancss
ccl
javancss
javancss
>
Cobertura plugin requires a new "psuedo-artifact"
-
Key: MEV-321
URL: http://jira.codehaus.org/browse/MEV-321
Project: Maven Evangelism
Type: Bug
Reporter: Mike Perham
The fix for MOJO-226 requires a c
The maven-cobertura-plugin team is pleased to announce the Cobertura
Plug-in
1.0 release!
http://maven-plugins.sourceforge.net/maven-cobertura-plugin
Maven Plugin for Cobertura
Changes in this version include:
To automatically install the plugin, type the following on a single
line
21 matches
Mail list logo
