[
https://issues.apache.org/jira/browse/QPIDJMS-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16082418#comment-16082418
]
ASF GitHub Bot commented on QPIDJMS-298:
----------------------------------------
Github user ctron commented on the issue:
https://github.com/apache/qpid-jms/pull/8
It indeed works fine. There is one caveat when converting Jacoco exec files
to XML. Only classes of the local module will be reported in the XML files. So
when you have a module A which gets tested by module B, then classes from
module A will be missing in the XML report of module B, although they are in
the exec file of module B.
However there is a maven plugin for fixing that:
https://ctron.github.io/jacoco-extras/xml-mojo.html 😉
> Use online service to manage and display coverage reports
> ---------------------------------------------------------
>
> Key: QPIDJMS-298
> URL: https://issues.apache.org/jira/browse/QPIDJMS-298
> Project: Qpid JMS
> Issue Type: Wish
> Components: qpid-jms-client, qpid-jms-discovery
> Affects Versions: 0.24.0
> Reporter: Jiri Danek
> Priority: Minor
>
> There are multiple coverage monitoring online services that integrate with
> popular CI services, like TravisCI.
> I propose uploading coverage report from run in TravisCI to some coverage
> monitoring service. This way, test coverage will become more visible.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
