|
Cobertura Maven Plug-in Status
Hello Codehaus Mojo Users,
Are there any active Cobertura Maven Plug-in developers? Project appears to be dead...
Regards,
Stevo.
|
|
Re: Cobertura Maven Plug-in Status
My understanding is that there is an issue with aggregating coverage results for a multi-module project and forking the build... Clover faces the same issue but is farther down the road, and it looks like there is no good solution for Maven 2.x (i.e. need the build plan stuff from 3.x)
The Cobertura plugin seems to work fine otherwise, why would it need a new release? -Stephen 2009/4/29 Stevo Slavić <sslavic@...>
Hello Codehaus Mojo Users,
Are there any active Cobertura Maven Plug-in developers? Project appears to be dead...
Regards,
Stevo.
|
|
Re: Cobertura Maven Plug-in Status
There is a point about classpath ordering (caused by some hashMap/linkedHashMap stuff) which is fixed in the current snapshot for exampleThat is to say : cobertura, when executing instrumented tests, is not using the same classpath as the one defined in maven (it could be problematic !...)
I think lots of other stuff have been fixed since the 2.2 release (which release date is dec 2007 !) Maybe current dev version is not enough stable to release ... but when I look at revision logs over SVN, I see the two last commits are dated from 21/12/2008 and 21/07/2008 :-(
It is too bad to use SNAPSHOT build in order to have this fixed.
Cheers, Frederic 2009/4/29 Stephen Connolly <stephen.alan.connolly@...>
My understanding is that there is an issue with aggregating coverage results for a multi-module project and forking the build...
Clover faces the same issue but is farther down the road, and it looks like there is no good solution for Maven 2.x (i.e. need the build plan stuff from 3.x)
The Cobertura plugin seems to work fine otherwise, why would it need a new release?
-Stephen
2009/4/29 Stevo Slavić <sslavic@...>
Hello Codehaus Mojo Users,
Are there any active Cobertura Maven Plug-in developers? Project appears to be dead...
Regards,
Stevo.
-- Frédéric Camblor
|
|
Re: Cobertura Maven Plug-in Status
I've asked because there seems to be a number of more or less important issues, very small number of issues has been resolved in last year, even tho at least some of the issues have high vote count and/or have patches from the community, like this one I'm currently most interested in where I'm proposing a new cobertura:report-only mojo to be added - currentl one can generate report only through cobertura:cobertura mojo which executes test phase in cobertura lifecycle so tests in integration-test phase do not get run; with cobertura:report-only mojo user has responsibility to instrument code and execute tests in whichever phase (s)he chooses.
About aggregating coverage results in a multimodule project, isn't it enough to - resolve this very long standing issue, by implementing support for cobertura:merge mojo & task;
- have users configure cobertura:instrument mojo at parent and thus inherited by every child;
- implement some new cobertura:aggregate report mojo which would (like report-only mojo bind to validate phase and) just call merge task before generating report for a parent project only?
Regards, Stevo. 2009/4/29 Stephen Connolly <stephen.alan.connolly@...>
My understanding is that there is an issue with aggregating coverage results for a multi-module project and forking the build...
Clover faces the same issue but is farther down the road, and it looks like there is no good solution for Maven 2.x (i.e. need the build plan stuff from 3.x)
The Cobertura plugin seems to work fine otherwise, why would it need a new release?
-Stephen
2009/4/29 Stevo Slavić <sslavic@...>
Hello Codehaus Mojo Users,
Are there any active Cobertura Maven Plug-in developers? Project appears to be dead...
Regards,
Stevo.
|
|
Re: Cobertura Maven Plug-in Status
One more IMO interesting new mojo would be "cobertura:save-coverage-data" which would help overcome obstacle Cobertura has (see last Q in Cobertura FAQ), when e.g. tests run in integration-test phase are actually functional (selenium) tests running against web application deployed in some embedded server started within maven build by a maven plugin, like Jetty. Currently Jetty server stops but as it runs in same JVM as Maven build, and because Cobertura writes coverage data only on JVM exit via shutdown hook, these data get written too late to be included in cobertura report. I would create jira issue, maybe even contribute implementation, but if there's no active developers to have a look at it and make a release all the effort would be in vain.
Regards, Stevo. 2009/4/29 Stevo Slavić <sslavic@...>
I've asked because there seems to be a number of more or less important issues, very small number of issues has been resolved in last year, even tho at least some of the issues have high vote count and/or have patches from the community, like this one I'm currently most interested in where I'm proposing a new cobertura:report-only mojo to be added - currentl one can generate report only through cobertura:cobertura mojo which executes test phase in cobertura lifecycle so tests in integration-test phase do not get run; with cobertura:report-only mojo user has responsibility to instrument code and execute tests in whichever phase (s)he chooses.
About aggregating coverage results in a multimodule project, isn't it enough to
- resolve this very long standing issue, by implementing support for cobertura:merge mojo & task;
- have users configure cobertura:instrument mojo at parent and thus inherited by every child;
- implement some new cobertura:aggregate report mojo which would (like report-only mojo bind to validate phase and) just call merge task before generating report for a parent project only?
Regards,
Stevo.
My understanding is that there is an issue with aggregating coverage results for a multi-module project and forking the build...Clover faces the same issue but is farther down the road, and it looks like there is no good solution for Maven 2.x (i.e. need the build plan stuff from 3.x)
The Cobertura plugin seems to work fine otherwise, why would it need a new release? -Stephen 2009/4/29 Stevo Slavić <sslavic@...>
Hello Codehaus Mojo Users,
Are there any active Cobertura Maven Plug-in developers? Project appears to be dead...
Regards,
Stevo.
|
|
Re: Cobertura Maven Plug-in Status
2009/4/29 Stevo Slavić <sslavic@...>
I've asked because there seems to be a number of more or less important issues, very small number of issues has been resolved in last year, even tho at least some of the issues have high vote count and/or have patches from the community, like this one I'm currently most interested in where I'm proposing a new cobertura:report-only mojo to be added - currentl one can generate report only through cobertura:cobertura mojo which executes test phase in cobertura lifecycle so tests in integration-test phase do not get run; with cobertura:report-only mojo user has responsibility to instrument code and execute tests in whichever phase (s)he chooses.
About aggregating coverage results in a multimodule project, isn't it enough to
- resolve this very long standing issue, by implementing support for cobertura:merge mojo & task;
- have users configure cobertura:instrument mojo at parent and thus inherited by every child;
- implement some new cobertura:aggregate report mojo which would (like report-only mojo bind to validate phase and) just call merge task before generating report for a parent project only?
You think this is the solution... but whe you try to roll a release, in the release:perform stage, either the aggregator parent module runs first, and there's no results to include, or it runs last (in which case it cannot be the parent and you have to put the config all over the place)...
the clover solution is to fork the build... but that just makes matters worse with everyone forking the build and a forked build only removing the forking plugin from the lifecycle and not removing any previous plugins that forked the build...
end result is that if you have N modules, you run the unit tests approx 2*N*(N-1) times at least... more if you have another plugin that forks the build... more still if you have a depth > 1
-Stephen
Regards,
Stevo.
My understanding is that there is an issue with aggregating coverage results for a multi-module project and forking the build...Clover faces the same issue but is farther down the road, and it looks like there is no good solution for Maven 2.x (i.e. need the build plan stuff from 3.x)
The Cobertura plugin seems to work fine otherwise, why would it need a new release? -Stephen 2009/4/29 Stevo Slavić <sslavic@...>
Hello Codehaus Mojo Users,
Are there any active Cobertura Maven Plug-in developers? Project appears to be dead...
Regards,
Stevo.
|
|
Re: Cobertura Maven Plug-in Status
Parent project could create initial empty cobertura.ser file, children modules could merge their coverage data into it. Question is how to get parent (aggregator module) to have report generated at the end of the whole build.
If such scenario is not naturally supported in Maven2, maybe a workaround would be to have plugin when executing report mojo for parent project actually just register a JVM shutdown hook (similarly to Cobertura) and generate report when Maven build successfully ends (if build fails, coverage report doesn't mean much anyway). This assumes that report generation will not fail, and if it does it won't fail a build (IMO just warning/error log feedback will suffice). Also, it assumes that plugin will, before registering shutdown hook, obtain and save reference for later to all necessary info needed for report generation so that generation doesn't fail because build has ended.
Regards, Stevo. 2009/4/29 Stephen Connolly <stephen.alan.connolly@...>
I've asked because there seems to be a number of more or less important issues, very small number of issues has been resolved in last year, even tho at least some of the issues have high vote count and/or have patches from the community, like this one I'm currently most interested in where I'm proposing a new cobertura:report-only mojo to be added - currentl one can generate report only through cobertura:cobertura mojo which executes test phase in cobertura lifecycle so tests in integration-test phase do not get run; with cobertura:report-only mojo user has responsibility to instrument code and execute tests in whichever phase (s)he chooses.
About aggregating coverage results in a multimodule project, isn't it enough to - resolve this very long standing issue, by implementing support for cobertura:merge mojo & task;
- have users configure cobertura:instrument mojo at parent and thus inherited by every child;
- implement some new cobertura:aggregate report mojo which would (like report-only mojo bind to validate phase and) just call merge task before generating report for a parent project only?
You think this is the solution... but whe you try to roll a release, in the release:perform stage, either the aggregator parent module runs first, and there's no results to include, or it runs last (in which case it cannot be the parent and you have to put the config all over the place)...
the clover solution is to fork the build... but that just makes matters worse with everyone forking the build and a forked build only removing the forking plugin from the lifecycle and not removing any previous plugins that forked the build...
end result is that if you have N modules, you run the unit tests approx 2*N*(N-1) times at least... more if you have another plugin that forks the build... more still if you have a depth > 1
-Stephen
Regards,
Stevo.
My understanding is that there is an issue with aggregating coverage results for a multi-module project and forking the build...Clover faces the same issue but is farther down the road, and it looks like there is no good solution for Maven 2.x (i.e. need the build plan stuff from 3.x)
The Cobertura plugin seems to work fine otherwise, why would it need a new release? -Stephen 2009/4/29 Stevo Slavić <sslavic@...>
Hello Codehaus Mojo Users,
Are there any active Cobertura Maven Plug-in developers? Project appears to be dead...
Regards,
Stevo.
|
|
Re: Cobertura Maven Plug-in Status
Hackedy-hackedy-hack! Maven 3.x with the build plan stuff will fix all these issues... and change the baby's nappy while it's at it ;-) -Stephen 2009/4/29 Stevo Slavić <sslavic@...>
Parent project could create initial empty cobertura.ser file, children modules could merge their coverage data into it. Question is how to get parent (aggregator module) to have report generated at the end of the whole build.
If such scenario is not naturally supported in Maven2, maybe a workaround would be to have plugin when executing report mojo for parent project actually just register a JVM shutdown hook (similarly to Cobertura) and generate report when Maven build successfully ends (if build fails, coverage report doesn't mean much anyway). This assumes that report generation will not fail, and if it does it won't fail a build (IMO just warning/error log feedback will suffice). Also, it assumes that plugin will, before registering shutdown hook, obtain and save reference for later to all necessary info needed for report generation so that generation doesn't fail because build has ended.
Regards, Stevo. 2009/4/29 Stephen Connolly <stephen.alan.connolly@...>
I've asked because there seems to be a number of more or less important issues, very small number of issues has been resolved in last year, even tho at least some of the issues have high vote count and/or have patches from the community, like this one I'm currently most interested in where I'm proposing a new cobertura:report-only mojo to be added - currentl one can generate report only through cobertura:cobertura mojo which executes test phase in cobertura lifecycle so tests in integration-test phase do not get run; with cobertura:report-only mojo user has responsibility to instrument code and execute tests in whichever phase (s)he chooses.
About aggregating coverage results in a multimodule project, isn't it enough to - resolve this very long standing issue, by implementing support for cobertura:merge mojo & task;
- have users configure cobertura:instrument mojo at parent and thus inherited by every child;
- implement some new cobertura:aggregate report mojo which would (like report-only mojo bind to validate phase and) just call merge task before generating report for a parent project only?
You think this is the solution... but whe you try to roll a release, in the release:perform stage, either the aggregator parent module runs first, and there's no results to include, or it runs last (in which case it cannot be the parent and you have to put the config all over the place)...
the clover solution is to fork the build... but that just makes matters worse with everyone forking the build and a forked build only removing the forking plugin from the lifecycle and not removing any previous plugins that forked the build...
end result is that if you have N modules, you run the unit tests approx 2*N*(N-1) times at least... more if you have another plugin that forks the build... more still if you have a depth > 1
-Stephen
Regards,
Stevo.
My understanding is that there is an issue with aggregating coverage results for a multi-module project and forking the build...Clover faces the same issue but is farther down the road, and it looks like there is no good solution for Maven 2.x (i.e. need the build plan stuff from 3.x)
The Cobertura plugin seems to work fine otherwise, why would it need a new release? -Stephen 2009/4/29 Stevo Slavić <sslavic@...>
Hello Codehaus Mojo Users,
Are there any active Cobertura Maven Plug-in developers? Project appears to be dead...
Regards,
Stevo.
|
|
Re: Cobertura Maven Plug-in Status
I agree it's a hack. Anyway, aggregate/merge support is one issue, what about all the others. Any thoughts on report-only mojo? Btw, surefire report plug-in has one too. Regards, Stevo.
2009/4/29 Stephen Connolly <stephen.alan.connolly@...>
Hackedy-hackedy-hack!
Maven 3.x with the build plan stuff will fix all these issues... and change the baby's nappy while it's at it
;-)-Stephen
2009/4/29 Stevo Slavić <sslavic@...>
Parent project could create initial empty cobertura.ser file, children modules could merge their coverage data into it. Question is how to get parent (aggregator module) to have report generated at the end of the whole build.
If such scenario is not naturally supported in Maven2, maybe a workaround would be to have plugin when executing report mojo for parent project actually just register a JVM shutdown hook (similarly to Cobertura) and generate report when Maven build successfully ends (if build fails, coverage report doesn't mean much anyway). This assumes that report generation will not fail, and if it does it won't fail a build (IMO just warning/error log feedback will suffice). Also, it assumes that plugin will, before registering shutdown hook, obtain and save reference for later to all necessary info needed for report generation so that generation doesn't fail because build has ended.
Regards, Stevo. 2009/4/29 Stephen Connolly <stephen.alan.connolly@...>
I've asked because there seems to be a number of more or less important issues, very small number of issues has been resolved in last year, even tho at least some of the issues have high vote count and/or have patches from the community, like this one I'm currently most interested in where I'm proposing a new cobertura:report-only mojo to be added - currentl one can generate report only through cobertura:cobertura mojo which executes test phase in cobertura lifecycle so tests in integration-test phase do not get run; with cobertura:report-only mojo user has responsibility to instrument code and execute tests in whichever phase (s)he chooses.
About aggregating coverage results in a multimodule project, isn't it enough to - resolve this very long standing issue, by implementing support for cobertura:merge mojo & task;
- have users configure cobertura:instrument mojo at parent and thus inherited by every child;
- implement some new cobertura:aggregate report mojo which would (like report-only mojo bind to validate phase and) just call merge task before generating report for a parent project only?
You think this is the solution... but whe you try to roll a release, in the release:perform stage, either the aggregator parent module runs first, and there's no results to include, or it runs last (in which case it cannot be the parent and you have to put the config all over the place)...
the clover solution is to fork the build... but that just makes matters worse with everyone forking the build and a forked build only removing the forking plugin from the lifecycle and not removing any previous plugins that forked the build...
end result is that if you have N modules, you run the unit tests approx 2*N*(N-1) times at least... more if you have another plugin that forks the build... more still if you have a depth > 1
-Stephen
Regards,
Stevo.
My understanding is that there is an issue with aggregating coverage results for a multi-module project and forking the build...Clover faces the same issue but is farther down the road, and it looks like there is no good solution for Maven 2.x (i.e. need the build plan stuff from 3.x)
The Cobertura plugin seems to work fine otherwise, why would it need a new release? -Stephen 2009/4/29 Stevo Slavić <sslavic@...>
Hello Codehaus Mojo Users,
Are there any active Cobertura Maven Plug-in developers? Project appears to be dead...
Regards,
Stevo.
|
|
Re: Cobertura Maven Plug-in Status
+1000 on report-only 2009/4/29 Stevo Slavić <sslavic@...>
I agree it's a hack. Anyway, aggregate/merge support is one issue, what about all the others. Any thoughts on report-only mojo? Btw, surefire report plug-in has one too.Regards,
Stevo.
2009/4/29 Stephen Connolly <stephen.alan.connolly@...>
Hackedy-hackedy-hack!
Maven 3.x with the build plan stuff will fix all these issues... and change the baby's nappy while it's at it
;-)-Stephen
2009/4/29 Stevo Slavić <sslavic@...>
Parent project could create initial empty cobertura.ser file, children modules could merge their coverage data into it. Question is how to get parent (aggregator module) to have report generated at the end of the whole build.
If such scenario is not naturally supported in Maven2, maybe a workaround would be to have plugin when executing report mojo for parent project actually just register a JVM shutdown hook (similarly to Cobertura) and generate report when Maven build successfully ends (if build fails, coverage report doesn't mean much anyway). This assumes that report generation will not fail, and if it does it won't fail a build (IMO just warning/error log feedback will suffice). Also, it assumes that plugin will, before registering shutdown hook, obtain and save reference for later to all necessary info needed for report generation so that generation doesn't fail because build has ended.
Regards, Stevo. 2009/4/29 Stephen Connolly <stephen.alan.connolly@...>
I've asked because there seems to be a number of more or less important issues, very small number of issues has been resolved in last year, even tho at least some of the issues have high vote count and/or have patches from the community, like this one I'm currently most interested in where I'm proposing a new cobertura:report-only mojo to be added - currentl one can generate report only through cobertura:cobertura mojo which executes test phase in cobertura lifecycle so tests in integration-test phase do not get run; with cobertura:report-only mojo user has responsibility to instrument code and execute tests in whichever phase (s)he chooses.
About aggregating coverage results in a multimodule project, isn't it enough to - resolve this very long standing issue, by implementing support for cobertura:merge mojo & task;
- have users configure cobertura:instrument mojo at parent and thus inherited by every child;
- implement some new cobertura:aggregate report mojo which would (like report-only mojo bind to validate phase and) just call merge task before generating report for a parent project only?
You think this is the solution... but whe you try to roll a release, in the release:perform stage, either the aggregator parent module runs first, and there's no results to include, or it runs last (in which case it cannot be the parent and you have to put the config all over the place)...
the clover solution is to fork the build... but that just makes matters worse with everyone forking the build and a forked build only removing the forking plugin from the lifecycle and not removing any previous plugins that forked the build...
end result is that if you have N modules, you run the unit tests approx 2*N*(N-1) times at least... more if you have another plugin that forks the build... more still if you have a depth > 1
-Stephen
Regards,
Stevo.
My understanding is that there is an issue with aggregating coverage results for a multi-module project and forking the build...Clover faces the same issue but is farther down the road, and it looks like there is no good solution for Maven 2.x (i.e. need the build plan stuff from 3.x)
The Cobertura plugin seems to work fine otherwise, why would it need a new release? -Stephen 2009/4/29 Stevo Slavić <sslavic@...>
Hello Codehaus Mojo Users,
Are there any active Cobertura Maven Plug-in developers? Project appears to be dead...
Regards,
Stevo.
|
|
Re: Cobertura Maven Plug-in Status
Mr Connolly, what's the status with report-only mojo, will there be a release of the cobertura maven plugin anytime soon, and what are the chances of having this mojo included in the next release?
Here is another solid reason to make a new cobertura plugin release. Not sure tho what's the policy regarding Java version in maven plugins, new Cobertura 1.9.1 seems to require Java 1.5.
Regards, Stevo. 2009/4/29 Stephen Connolly <stephen.alan.connolly@...>
+1000 on report-only2009/4/29 Stevo Slavić <sslavic@...>
I agree it's a hack. Anyway, aggregate/merge support is one issue, what about all the others. Any thoughts on report-only mojo? Btw, surefire report plug-in has one too.Regards,
Stevo.
2009/4/29 Stephen Connolly <stephen.alan.connolly@...>
Hackedy-hackedy-hack!
Maven 3.x with the build plan stuff will fix all these issues... and change the baby's nappy while it's at it
;-)-Stephen
2009/4/29 Stevo Slavić <sslavic@...>
Parent project could create initial empty cobertura.ser file, children modules could merge their coverage data into it. Question is how to get parent (aggregator module) to have report generated at the end of the whole build.
If such scenario is not naturally supported in Maven2, maybe a workaround would be to have plugin when executing report mojo for parent project actually just register a JVM shutdown hook (similarly to Cobertura) and generate report when Maven build successfully ends (if build fails, coverage report doesn't mean much anyway). This assumes that report generation will not fail, and if it does it won't fail a build (IMO just warning/error log feedback will suffice). Also, it assumes that plugin will, before registering shutdown hook, obtain and save reference for later to all necessary info needed for report generation so that generation doesn't fail because build has ended.
Regards, Stevo. 2009/4/29 Stephen Connolly <stephen.alan.connolly@...>
I've asked because there seems to be a number of more or less important issues, very small number of issues has been resolved in last year, even tho at least some of the issues have high vote count and/or have patches from the community, like this one I'm currently most interested in where I'm proposing a new cobertura:report-only mojo to be added - currentl one can generate report only through cobertura:cobertura mojo which executes test phase in cobertura lifecycle so tests in integration-test phase do not get run; with cobertura:report-only mojo user has responsibility to instrument code and execute tests in whichever phase (s)he chooses.
About aggregating coverage results in a multimodule project, isn't it enough to - resolve this very long standing issue, by implementing support for cobertura:merge mojo & task;
- have users configure cobertura:instrument mojo at parent and thus inherited by every child;
- implement some new cobertura:aggregate report mojo which would (like report-only mojo bind to validate phase and) just call merge task before generating report for a parent project only?
You think this is the solution... but whe you try to roll a release, in the release:perform stage, either the aggregator parent module runs first, and there's no results to include, or it runs last (in which case it cannot be the parent and you have to put the config all over the place)...
the clover solution is to fork the build... but that just makes matters worse with everyone forking the build and a forked build only removing the forking plugin from the lifecycle and not removing any previous plugins that forked the build...
end result is that if you have N modules, you run the unit tests approx 2*N*(N-1) times at least... more if you have another plugin that forks the build... more still if you have a depth > 1
-Stephen
Regards,
Stevo.
My understanding is that there is an issue with aggregating coverage results for a multi-module project and forking the build...Clover faces the same issue but is farther down the road, and it looks like there is no good solution for Maven 2.x (i.e. need the build plan stuff from 3.x)
The Cobertura plugin seems to work fine otherwise, why would it need a new release? -Stephen 2009/4/29 Stevo Slavić <sslavic@...>
Hello Codehaus Mojo Users,
Are there any active Cobertura Maven Plug-in developers? Project appears to be dead...
Regards,
Stevo.
|
|
Re: Cobertura Maven Plug-in Status
I ain't working on cobertura-maven-plugin... I think it's Garvin you're after...
P.S.
anywho I don't use Mr...
I prefer not to use any titles... but if you are crazy enough to try and use a title, please use the correct title... I didn't spend an extra 3 years in college for nothing ;-)
Sent from my [rhymes with myPod] ;-) On 27 May 2009, at 02:28, Stevo Slavić < sslavic@...> wrote: Mr Connolly, what's the status with report-only mojo, will there be a release of the cobertura maven plugin anytime soon, and what are the chances of having this mojo included in the next release?
Here is another solid reason to make a new cobertura plugin release. Not sure tho what's the policy regarding Java version in maven plugins, new Cobertura 1.9.1 seems to require Java 1.5.
Regards, Stevo. 2009/4/29 Stephen Connolly <stephen.alan.connolly@...>
+1000 on report-only2009/4/29 Stevo Slavić <sslavic@...>
I agree it's a hack. Anyway, aggregate/merge support is one issue, what about all the others. Any thoughts on report-only mojo? Btw, surefire report plug-in has one too.Regards,
Stevo.
2009/4/29 Stephen Connolly <stephen.alan.connolly@...>
Hackedy-hackedy-hack!
Maven 3.x with the build plan stuff will fix all these issues... and change the baby's nappy while it's at it
;-)-Stephen
2009/4/29 Stevo Slavić <sslavic@...>
Parent project could create initial empty cobertura.ser file, children modules could merge their coverage data into it. Question is how to get parent (aggregator module) to have report generated at the end of the whole build.
If such scenario is not naturally supported in Maven2, maybe a workaround would be to have plugin when executing report mojo for parent project actually just register a JVM shutdown hook (similarly to Cobertura) and generate report when Maven build successfully ends (if build fails, coverage report doesn't mean much anyway). This assumes that report generation will not fail, and if it does it won't fail a build (IMO just warning/error log feedback will suffice). Also, it assumes that plugin will, before registering shutdown hook, obtain and save reference for later to all necessary info needed for report generation so that generation doesn't fail because build has ended.
Regards, Stevo. 2009/4/29 Stephen Connolly <stephen.alan.connolly@...>
I've asked because there seems to be a number of more or less important issues, very small number of issues has been resolved in last year, even tho at least some of the issues have high vote count and/or have patches from the community, like this one I'm currently most interested in where I'm proposing a new cobertura:report-only mojo to be added - currentl one can generate report only through cobertura:cobertura mojo which executes test phase in cobertura lifecycle so tests in integration-test phase do not get run; with cobertura:report-only mojo user has responsibility to instrument code and execute tests in whichever phase (s)he chooses.
About aggregating coverage results in a multimodule project, isn't it enough to - resolve this very long standing issue, by implementing support for cobertura:merge mojo & task;
- have users configure cobertura:instrument mojo at parent and thus inherited by every child;
- implement some new cobertura:aggregate report mojo which would (like report-only mojo bind to validate phase and) just call merge task before generating report for a parent project only?
You think this is the solution... but whe you try to roll a release, in the release:perform stage, either the aggregator parent module runs first, and there's no results to include, or it runs last (in which case it cannot be the parent and you have to put the config all over the place)...
the clover solution is to fork the build... but that just makes matters worse with everyone forking the build and a forked build only removing the forking plugin from the lifecycle and not removing any previous plugins that forked the build...
end result is that if you have N modules, you run the unit tests approx 2*N*(N-1) times at least... more if you have another plugin that forks the build... more still if you have a depth > 1
-Stephen
Regards,
Stevo.
My understanding is that there is an issue with aggregating coverage results for a multi-module project and forking the build...Clover faces the same issue but is farther down the road, and it looks like there is no good solution for Maven 2.x (i.e. need the build plan stuff from 3.x)
The Cobertura plugin seems to work fine otherwise, why would it need a new release? -Stephen 2009/4/29 Stevo Slavić <sslavic@...>
Hello Codehaus Mojo Users,
Are there any active Cobertura Maven Plug-in developers? Project appears to be dead...
Regards,
Stevo.
|
|
Re: Cobertura Maven Plug-in Status
I vote +1 for initiating a vote for release 2.3 :o)
I agree with Stevo, this release does not require the report-only mojo to be resolved.
|
|
Re: Cobertura Maven Plug-in Status
After getting support for cobertura 1.9.1 included, I prefer report-only mojo more than anything else to be part of next release. Don't see a reason why it shouldn't be. It would be good to get feedback from the mojo maintainer(s) on release plans.
Regards, Stevo. On Fri, Jun 5, 2009 at 2:49 PM, Simon Brandhof <simon.brandhof@...> wrote:
I vote +1 for initiating a vote for release 2.3 :o)
I agree with Stevo, this release does not require the report-only mojo to be resolved.
|
