[
http://jira.codehaus.org/browse/MCOBERTURA-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stevo Slavic updated MCOBERTURA-138:
------------------------------------
Attachment: cobertura-maven-plugin-MCOBERTURA-138.patch
Renamed patch to [^cobertura-maven-plugin-MCOBERTURA-138.patch]
> Add support for configuring cobertura output directory and flag whether that
> directory should be used as build output directory
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: MCOBERTURA-138
> URL: http://jira.codehaus.org/browse/MCOBERTURA-138
> Project: Maven 2.x Cobertura Plugin
> Issue Type: Improvement
> Affects Versions: 2.4
> Reporter: Stevo Slavic
> Attachments: cobertura-maven-plugin-MCOBERTURA-138.patch
>
>
> cobertura-maven-plugin v2.4 instrument goal had hardcoded cobertura output
> directory path. Also, it always would switch build output directory to
> cobertura output directory. This is OK as a convention, but configuration
> option should be provided. Attached patch
> [^cobertura-maven-plugin-MCOBERTURA-137.patch] adds support for configuring
> these two options. Also this will enable users to configure instrumentation
> goal not to affect other executions of non-coverage related plugins when
> code, tests and coverage gathering is in same Maven module.
> Special care has been taken for backward compatibility, so same output
> directory is used by default, and build output directory is switched to
> cobertura output directory by default - just like before this change.
> A test case has been added, and all existing tests including integration
> tests pass.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.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