Releases: jacoco/jacoco
Releases · jacoco/jacoco
0.7.4
0.7.3
New Features
- For offline instrumemtation agent configuration supports system properties replacements. Implementation based on pull request of GitHub user 'debugger' (GitHub #262).
- Exclude dynamically generated classes from instrumentation for better interoperability with JMockit, analysis contributed by Rogério Liesenfeld (GitHub #272).
Fixed Bugs
- Instrumented bytecode now compatible with Android ART runtime, analysis and fix contributed by Allen Hair (GitHub #265).
0.7.2
Fixed Bugs
- Do not ignore synthetic lambda methods to get code coverage for Java 8 lambda expressions (GitHub #232).
New Features
0.7.1
0.7.0
0.6.5
New Features
- Warnings are logged during report generation if different versions of classes are used than at runtime (GitHub #185).
- Signatures are removed from instrumented JAR files (GitHub #186).
Fixed Bugs
- Skip jacoco instrumentation for mvn modules with package type ear (GitHub #169).
- Align skip conditions and messages for Maven goals and give reasons. This includes removal of the specific skip condition for packages e.g. POMs and instead checks existence of target/classes in appropriate goals (GitHub #171).
- GitHub #44: (Regression) Agent Mojo should set empty property, if execution was skipped (GitHub #192).
API Changes
- Restrict visibility of methods in abstract classes of jacoco-maven-plugin (GitHub #175).
0.6.4
New Features
- Support for Android Strict Mode (GitHub #113).
- New
dumpMojo for Maven plug-in (GitHub #107). - New
mergeMojo for Maven plug-in, contributed by Mads Mohr Christensen (GitHub #126). - Additional list of source files for every package in HTML report (GitHub #142).
- Additional
report-integrationandprepare-agent-integrationgoals for integration tests. (GitHub #152, #161).
Fixed Bugs
- Multiple executions of Maven goal
prepare-agentshould not lead to incorrect configuration (GitHub #40). - Avoid direct dependency on java.lang.management APIs to allow usage on Android (GitHub #150).
- All JaCoCo Maven goals are marked as thread-safe (GitHub #133).
checkandmergegoal failures in jacoco-maven-plugin with Maven 2.2.1 due to incompatible configuration (GitHub #129).
API Changes
- New API package
org.jacoco.core.toolsfor shared high-level tools. (GitHub #159).
0.6.3
New Features
- Support for archives in Pack200 format (GitHub #91).
- The coverage check has been reworked to allow checks on all counter values on all element types (GitHub #106).
- Coverage checks are now also available in Ant (GitHub #106).
Fixed Bugs
- Fixed inconsistent stackmap frames when instrumenting class files produced by certain tools like ProGuard (GitHub #85).
Non-functional Changes
- More context information when exceptions occur during analysis or instrumentation (GitHub #104).
- If analysis is performed on offline instrumented classes - which is an build configuration error - an exception is now thrown (GitHub #108).
API Changes
0.6.2
New Features
- Support for offline instrumentation (GitHub #4, #64).
JaCoCo agent exposes runtime API for direct integration with application under test (GitHub #61). - Support for parallel test execution: Different agents can now safely write to the same *.exec file (GitHub #52).
- New output mode 'none' can be used when agent is only controlled via JMX or its new runtime API (GitHub #63).
- Better error message in case of invalid stackmap frames (GitHub #73).
- jacoco-maven-plugin: default phase for goal "report" - "verify" (GitHub #72).
Non-functional Changes
- For every build the corresponding Git commit hash is included as Eclipse-SourceReferences manifest headers (GitHub #7, #59).
- Adjust saturation of red source highlighting in HTML reports to make JaCoCo reports more accessible to red/green blind users.
API Changes
- The output mode mbean of the agent has been dropped in favor of the new boolean option jmx. This allows to combine JMX access with any other output mode (GitHub #62).
0.6.1
New Features
- Add a coverage check Mojo, contributed by Kyle Lieber (GitHub #6).
Fixed Bugs
- jacocoant.jar should not conflict with ASM 3.x (GitHub #39).
- Agent Mojo should set empty property, if execution was skipped (GitHub #44).