db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5817) Add support for the JaCoCo code coverage tool
Date Mon, 18 Jun 2012 11:26:44 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kristian Waagan updated DERBY-5817:
-----------------------------------

    Attachment: derby-5817-1c-jacoco_support.diff

Attaching patch 1c, which further improves the JaCoCo support in build.xml.

I refactored some code related to getting the svn version, because I'm adding the version
to the report title.

I updated the report at people.apache.org/~kristwaa/jacoco/ with the results produced by patch
1c and the target jacoco-complete.

I think the EMMA results include coverage data from runs with several different JVM versions.
I have not added support for that, but assuming the merged.exec file is kept from each run
a separate merge/report target can be used.

Patch ready for review.
                
> Add support for the JaCoCo code coverage tool
> ---------------------------------------------
>
>                 Key: DERBY-5817
>                 URL: https://issues.apache.org/jira/browse/DERBY-5817
>             Project: Derby
>          Issue Type: Task
>          Components: Miscellaneous, Test
>    Affects Versions: 10.10.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>         Attachments: derby-5817-1a-jacoco_support.diff, derby-5817-1b-jacoco_support.diff,
derby-5817-1c-jacoco_support.diff
>
>
> Add support for the JaCoCo code coverage tool ([1]).
> While we are currently relying on EMMA for code coverage, the tool isn't being maintained.
It works nicely for the time being, but having additional support for a tool that's being
actively developed and maintained would be nice.
> [1] http://www.eclemma.org/jacoco/

--
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

        

Mime
View raw message