[ http://jira.codehaus.org/browse/MCOBERTURA-57?page=comments#action_82425 ] Joakim Erdfelt commented on MCOBERTURA-57: ------------------------------------------
Due to the embedded nature of the cobetura.ser file with cobertura 1.8. (the instrumented classes have the cobertura.ser file location embedded in the class) doing an aggregate or merge (either by action of the user, or internal usage of those bits by cobertura or the plugin) the cobertura.ser data can get out of sync and produce invalid results (usually manifested in 0% or 100% coverages, or missing classes in the report). Moving the file as part of a single project execution is safe, but once you get into unit + integration tests, or multi-project builds, or reactor builds, or using external tools such as QALabs, you'll encounter issues. This hack addresses a small set of bugs. The next cobertura has many overhauls to the configuration. (cobertura.ser file location, and ignores / excludes definitions to name some of the big ones) This is not the first time this hack has been introduced to cobertura. It existed before. And was removed for causing problems. > Workaround for cobertura.ser location > ------------------------------------- > > Key: MCOBERTURA-57 > URL: http://jira.codehaus.org/browse/MCOBERTURA-57 > Project: Maven 2.x Cobertura Plugin > Issue Type: Improvement > Affects Versions: 2.0 > Reporter: fabrizio giustina > Assigned To: fabrizio giustina > Fix For: 2.1 > > > Cobertura 1.8 doesn't allow to set the location of cobertura.ser properly. > It's always created in the project root and we can't explicitly force it to > be in /target. > Implemented a workaround so that file is moved to target by the mojo. -- 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
