v30.0.1

• [fix] report-generator: Fixed Gradle module metadata which resulted in Could not find org.jacoco.agent-0.8.8-runtime

v30.0.0

• [breaking change] teamscale-maven-plugin: Made plugin compatible with surefire 3.0.0. Replace the teamscale-surefire-provider dependency with impacted-test-engine in your pom.xml files.
• [feature] teamscale-gradle-plugin, teamscale-maven-plugin: Added ability to pass excluded test engines to impacted test engine
• [fix] teamscale-maven-plugin: Testwise coverage uploads were performed per test cluster instead of one upload after all tests
• [fix] teamscale-gradle-plugin, teamscale-maven-plugin: Impacted tests were requested once for each test engine
• [fix] teamscale-gradle-plugin, teamscale-maven-plugin: Execution of impacted tests failed when test names were unstable i.e. parameterized tests with parameters that are not serializeable

v29.1.3

• [fix] http control server was not correctly shut down after the tests ended

v29.1.2

• [fix] teamscale-maven-plugin: Partition was not correctly provided to the impacted test engine
• [fix] tia-client: Semicolons in test names were not correctly sent to the Teamscale JaCoCo Agent

v29.1.1

• [fix] teamscale-gradle-plugin, teamscale-maven-plugin, teamscale-jacoco-agent: Tooling did not provide a way to set the partial flag

v29.1.0

• [feature] teamscale-gradle-plugin: Allow parallel test execution with testwise coverage collection
• [fix] teamscale-gradle-plugin: Verify that maxParallelForks is 1
• [fix] impacted-test-engine: Provide sane fallback for non-supported test engines

v29.0.0

• [fix] Fixed the prefix extraction pattern and the partition pattern for Artifactory in the agent's documentation
• [fix/breaking change] teamscale-client, teamscale-gradle-plugin, teamscale-maven-plugin, teamscale-jacoco-agent: Teamscale 8.0 introduced the concept of execution units. To distinguish them from normal, singular test executions, the -test-exection- and -execution-unit- uniform path prefixes were introduced. This broke gradle and maven test runner plugins because the actual test paths and Teamscale's uniform paths did not match anymore. To prevent this, testName is now exposed by the teamscale client and used by the plugins which corresponds to the uniform path without the prefixes. If you're using the client, or listen to the /testrun/start API from the Teamscale JaCoCo agent, this is a breaking change. You now need to use testName in your runner, not the uniformPath.

v28.0.0

• [breaking change] removed support for JavaWS
• [fix] Fixed git.properties detection when directories are on the classpath

v27.0.2

• [fix] Updated dependencies (Fixes #225, CVE-2022-42889)

v27.0.1

• [fix] teamscale-gradle-plugin: Property 'outputLocation' is declared as an output property of Report xml (type TaskGeneratedSingleFileReport) but does not have a task associated with it.