HTTP parallel request option

0.4.2

Parallelization support for Maven 0.4.2

First Performance Release

0.4.0

Parallelization support for Maven

Support for JDK19

0.3.2

Prepares release 0.3.2

Event Listener Fix

Fix for

Caused by: org.gradle.internal.event.ListenerNotificationException: Failed to notify project evaluation listener.

Refactor to SBT

1. Refactoring - Current version still has a lot of code that can be reused.
2. Option OMNI_LOG with environment variable. Logs everything into target/omni.log file (Not configurable yet)
3. Read JSON configuration method

Interop

1. Interoperability

• Important Static methods made available to Clojure and Java
• Reduction of the need to create instances on the fly.

3. LCov Expected Values Parsing Improvements - The absence of some values would generate an unwanted exception
4. Clojure's language support

This release contains breaking changes because it now supports interoperability between Kotlin and other JVM languages

Restriction Release

1. Remove possibility to send unknown reports in Omni to Codecov. Unfortunately Codecov crashes with unknown reports. The only way to check the correct format of the report is essentially to provide the implementation to do that. In this way report sending to Codecov becomes restricted to the known formats to Omni.
2. Remove banned file name list - Since the algorithm no longer relies on the filename, it doesn't make sense anymore to keep doing that. Therefore, the banned list is removed.

Url Fix for BitBucket

Url Fix for BitBucket

Support for More Pipelines

1. Reports in the same folder are merged and average, (We assume thart if there are different reports in the same folder, it only means that there are different brands in there.) Unfortunately, by doing so, the results may become inconsistent for reports that do not report coverage for certain
   files. Please make sure not to have different report brands (i.e. Clover and LCov together) for the same files. In that case, line coverage will be reported duplicate.
2. Exclude report option reportRejectList. Given the above, it may be difficult to manage that situation. We can then use this option to exclude a report that for some reason we don't want to consider for the overall coverage calculation). See example in .
3. Change file detection to include content. The check should be based on text labels and parsing should be avoided.
4. Remove files from the excluded list where applicable (code wise). Files in de excluded list are also used in a filename based algorithm. This needs to be changed. - I leave it there because coverage-final.json is not a part of any other report default naming strategy. This way I keep this protection.
5. Add support for Circle CI and BitBucket builds

fetchBranchNameFromEnv

Create flag fetchBranchNameFromEnv to fetch the branch name from environment variables
Fix Reporting sending of test report files by default with ignoreTestBuildDirectory
Fix Codacy not including TSX in TypeScript reports