You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Tan Quach (JIRA)" <ji...@apache.org> on 2012/08/07 21:04:10 UTC
[jira] [Created] (BUILDR-649) Running cobertura:html on a project
with sub-modules does not generate a complete report
Tan Quach created BUILDR-649:
--------------------------------
Summary: Running cobertura:html on a project with sub-modules does not generate a complete report
Key: BUILDR-649
URL: https://issues.apache.org/jira/browse/BUILDR-649
Project: Buildr
Issue Type: Bug
Components: Extensions
Affects Versions: 1.4.7
Environment: Windows 7, Ubuntu 12.04
Reporter: Tan Quach
Having multiple projects with inter-dependencies will not produce a complete Cobertura test coverage report.
It seems when more than one project has a dependency on a single project, the reports are blown away. I've set up a sample project here:
https://github.com/tantastik/sample-buildr-repo
If you clone this locally and run "buildr cobertura:html" you will find that the sources from the "common" project are not included in the report, however all sources from the "app" and "webapp" projects are included.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (BUILDR-649) Running cobertura:html on a project
with sub-modules does not generate a complete report
Posted by "Tan Quach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tan Quach updated BUILDR-649:
-----------------------------
Attachment: out.log
Here's a trace log of the output from:
buildr clean cobertura:html --trace
> Running cobertura:html on a project with sub-modules does not generate a complete report
> ----------------------------------------------------------------------------------------
>
> Key: BUILDR-649
> URL: https://issues.apache.org/jira/browse/BUILDR-649
> Project: Buildr
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.4.7
> Environment: Windows 7, Ubuntu 12.04
> Reporter: Tan Quach
> Attachments: out.log
>
>
> Having multiple projects with inter-dependencies will not produce a complete Cobertura test coverage report.
> It seems when more than one project has a dependency on a single project, the reports are either not generated or are not instrumented in the proper place. I've set up a sample project here:
> https://github.com/tantastik/sample-buildr-repo
> In this sample project there are 3 modules: common, app, webapp.
> - 'common' has no project dependencies
> - 'app' depends on 'common'
> - 'webapp' depends on 'common' and 'app'
> When running cobertura:html from the root directory, the subsequent html report does not contain classes from the 'common' project.
> If you clone this locally and run "buildr cobertura:html" you will see this behaviour.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (BUILDR-649) Running cobertura:html on a project
with sub-modules does not generate a complete report
Posted by "Tan Quach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tan Quach updated BUILDR-649:
-----------------------------
Description:
Having multiple projects with inter-dependencies will not produce a complete Cobertura test coverage report.
It seems when more than one project has a dependency on a single project, the reports are either not generated or are not instrumented in the proper place. I've set up a sample project here:
https://github.com/tantastik/sample-buildr-repo
In this sample project there are 3 modules: common, app, webapp.
- 'common' has no project dependencies
- 'app' depends on 'common'
- 'webapp' depends on 'common' and 'app'
When running cobertura:html from the root directory, the subsequent html report does not contain classes from the 'common' project.
If you clone this locally and run "buildr cobertura:html" you will see this behaviour.
was:
Having multiple projects with inter-dependencies will not produce a complete Cobertura test coverage report.
It seems when more than one project has a dependency on a single project, the reports are either not generated or are not instrumented in the proper place. I've set up a sample project here:
https://github.com/tantastik/sample-buildr-repo
In this sample project there are 3 modules: common, app, webapp.
- 'common' has no project dependencies
- 'app' depends on common
- 'webapp' depends on 'common' and 'app'
When running cobertura:html from the root directory, the subsequent html report does not contain classes from the 'common' project.
If you clone this locally and run "buildr cobertura:html" you will see this behaviour.
> Running cobertura:html on a project with sub-modules does not generate a complete report
> ----------------------------------------------------------------------------------------
>
> Key: BUILDR-649
> URL: https://issues.apache.org/jira/browse/BUILDR-649
> Project: Buildr
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.4.7
> Environment: Windows 7, Ubuntu 12.04
> Reporter: Tan Quach
>
> Having multiple projects with inter-dependencies will not produce a complete Cobertura test coverage report.
> It seems when more than one project has a dependency on a single project, the reports are either not generated or are not instrumented in the proper place. I've set up a sample project here:
> https://github.com/tantastik/sample-buildr-repo
> In this sample project there are 3 modules: common, app, webapp.
> - 'common' has no project dependencies
> - 'app' depends on 'common'
> - 'webapp' depends on 'common' and 'app'
> When running cobertura:html from the root directory, the subsequent html report does not contain classes from the 'common' project.
> If you clone this locally and run "buildr cobertura:html" you will see this behaviour.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (BUILDR-649) Running cobertura:html on a project
with sub-modules does not generate a complete report
Posted by "Peter Donald (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Donald updated BUILDR-649:
--------------------------------
Fix Version/s: 1.5
> Running cobertura:html on a project with sub-modules does not generate a complete report
> ----------------------------------------------------------------------------------------
>
> Key: BUILDR-649
> URL: https://issues.apache.org/jira/browse/BUILDR-649
> Project: Buildr
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.4.7
> Environment: Windows 7, Ubuntu 12.04
> Reporter: Tan Quach
> Fix For: 1.5
>
> Attachments: out.log
>
>
> Having multiple projects with inter-dependencies will not produce a complete Cobertura test coverage report.
> It seems when more than one project has a dependency on a single project, the reports are either not generated or are not instrumented in the proper place. I've set up a sample project here:
> https://github.com/tantastik/sample-buildr-repo
> In this sample project there are 3 modules: common, app, webapp.
> - 'common' has no project dependencies
> - 'app' depends on 'common'
> - 'webapp' depends on 'common' and 'app'
> When running cobertura:html from the root directory, the subsequent html report does not contain classes from the 'common' project.
> If you clone this locally and run "buildr cobertura:html" you will see this behaviour.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (BUILDR-649) Running cobertura:html on a project
with sub-modules does not generate a complete report
Posted by "Tan Quach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tan Quach updated BUILDR-649:
-----------------------------
Attachment: out.log
> Running cobertura:html on a project with sub-modules does not generate a complete report
> ----------------------------------------------------------------------------------------
>
> Key: BUILDR-649
> URL: https://issues.apache.org/jira/browse/BUILDR-649
> Project: Buildr
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.4.7
> Environment: Windows 7, Ubuntu 12.04
> Reporter: Tan Quach
> Attachments: out.log
>
>
> Having multiple projects with inter-dependencies will not produce a complete Cobertura test coverage report.
> It seems when more than one project has a dependency on a single project, the reports are either not generated or are not instrumented in the proper place. I've set up a sample project here:
> https://github.com/tantastik/sample-buildr-repo
> In this sample project there are 3 modules: common, app, webapp.
> - 'common' has no project dependencies
> - 'app' depends on 'common'
> - 'webapp' depends on 'common' and 'app'
> When running cobertura:html from the root directory, the subsequent html report does not contain classes from the 'common' project.
> If you clone this locally and run "buildr cobertura:html" you will see this behaviour.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (BUILDR-649) Running cobertura:html on a project
with sub-modules does not generate a complete report
Posted by "Tan Quach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tan Quach updated BUILDR-649:
-----------------------------
Description:
Having multiple projects with inter-dependencies will not produce a complete Cobertura test coverage report.
It seems when more than one project has a dependency on a single project, the reports are either not generated or are not instrumented in the proper place. I've set up a sample project here:
https://github.com/tantastik/sample-buildr-repo
In this sample project there are 3 modules: common, app, webapp.
- 'common' has no project dependencies
- 'app' depends on common
- 'webapp' depends on 'common' and 'app'
When running cobertura:html from the root directory, the subsequent html report does not contain classes from the 'common' project.
If you clone this locally and run "buildr cobertura:html" you will see this behaviour.
was:
Having multiple projects with inter-dependencies will not produce a complete Cobertura test coverage report.
It seems when more than one project has a dependency on a single project, the reports are blown away. I've set up a sample project here:
https://github.com/tantastik/sample-buildr-repo
If you clone this locally and run "buildr cobertura:html" you will find that the sources from the "common" project are not included in the report, however all sources from the "app" and "webapp" projects are included.
> Running cobertura:html on a project with sub-modules does not generate a complete report
> ----------------------------------------------------------------------------------------
>
> Key: BUILDR-649
> URL: https://issues.apache.org/jira/browse/BUILDR-649
> Project: Buildr
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.4.7
> Environment: Windows 7, Ubuntu 12.04
> Reporter: Tan Quach
>
> Having multiple projects with inter-dependencies will not produce a complete Cobertura test coverage report.
> It seems when more than one project has a dependency on a single project, the reports are either not generated or are not instrumented in the proper place. I've set up a sample project here:
> https://github.com/tantastik/sample-buildr-repo
> In this sample project there are 3 modules: common, app, webapp.
> - 'common' has no project dependencies
> - 'app' depends on common
> - 'webapp' depends on 'common' and 'app'
> When running cobertura:html from the root directory, the subsequent html report does not contain classes from the 'common' project.
> If you clone this locally and run "buildr cobertura:html" you will see this behaviour.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (BUILDR-649) Running cobertura:html on a project
with sub-modules does not generate a complete report
Posted by "Tan Quach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tan Quach updated BUILDR-649:
-----------------------------
Attachment: (was: out.log)
> Running cobertura:html on a project with sub-modules does not generate a complete report
> ----------------------------------------------------------------------------------------
>
> Key: BUILDR-649
> URL: https://issues.apache.org/jira/browse/BUILDR-649
> Project: Buildr
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.4.7
> Environment: Windows 7, Ubuntu 12.04
> Reporter: Tan Quach
> Attachments: out.log
>
>
> Having multiple projects with inter-dependencies will not produce a complete Cobertura test coverage report.
> It seems when more than one project has a dependency on a single project, the reports are either not generated or are not instrumented in the proper place. I've set up a sample project here:
> https://github.com/tantastik/sample-buildr-repo
> In this sample project there are 3 modules: common, app, webapp.
> - 'common' has no project dependencies
> - 'app' depends on 'common'
> - 'webapp' depends on 'common' and 'app'
> When running cobertura:html from the root directory, the subsequent html report does not contain classes from the 'common' project.
> If you clone this locally and run "buildr cobertura:html" you will see this behaviour.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira