[
https://jira.codehaus.org/browse/MCOBERTURA-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shant Stepanian updated MCOBERTURA-83:
--------------------------------------
Attachment: reportOnlyAndInstrumentOutputDirPatch.patch
Agreed w/ Christoph on this - various clients may have different use cases, and
so the plugin should not force this behavior on everyone. There are many
requests on this JIRA ticket and others (not to mention that this JIRA now
references patches from 4 people who tried to solve this issue), so it seems
like it should be addressed in the next version and it would benefit a lot of
people.
In addition, I noticed that the "instrument" goal was changing the build output
directory to the instrumented directory. This had negative consequences on our
project as the jar plugin was now packaging the instrumented files. I've
replaced my previous patch w/ a new one that configures the output directory
change as a configuration parameter.
In general, it seems like there should be two usages of this plugin:
* via the cobertura goal, which essentially does everything for you
* via specific usage of the instrument and "report" goals, which allows finer
grained control, including the ability to not run your tests twice. The last
patch I had on not changing the outputDirectory goes along with this
Please let us know when these changes can be added. I'd be willing to work w/
someone on this
Thanks,
Shant
> Can't run install and cobertura:cobertura without running test phase twice
> --------------------------------------------------------------------------
>
> Key: MCOBERTURA-83
> URL: https://jira.codehaus.org/browse/MCOBERTURA-83
> Project: Maven 2.x Cobertura Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Hugo Palma
> Priority: Critical
> Attachments: patch, reportOnlyAndInstrumentOutputDirPatch.patch,
> report-only.patch
>
>
> I want run as part of my CI process the goals:
> mvn install cobertura:cobertura
> The problem is that this causes the test phase to be ran twice.
> AFAIK, there's no way to do this and it's a major issue when doing CI.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
