Migrating gradle plugin from v2.0.1 to v2.2.2 requires additional configuration

[Thevakumar-Luheerathan]

Description:
Currently, we are using v2.0.1 gradle plugin in some repositories(Eg : io). When migrating from v2.0.1 to v2.2.2, we need to add following configuration/similar configuration to the root project build.gradle file.

subprojects {

    configurations {
        jbalTools
    }
    dependencies {
        jbalTools ("org.ballerinalang:jballerina-tools:${ballerinaLangVersion}") {
            transitive = false
        }
    }
}

Steps to reproduce:

Affected Versions:

OS, DB, other environment details and versions:

Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

[Thevakumar-Luheerathan]

This is need to check the performance gain, test failures with the test parallelisation feature on standard libraries. We are planning to release this feature for update 9.

[TharmiganK]

Isn't it better to release a gradle plugin with the following change and then update the plugin version in standard libraries: ballerina-platform/plugin-gradle#134
Otherwise we need to do another iteration to update the plugin version to support parallel test execution
@ThisaruGuruge @Thevakumar-Luheerathan WDYT?

[Thevakumar-Luheerathan]

Isn't it better to release a gradle plugin with the following change and then update the plugin version in standard libraries: ballerina-platform/plugin-gradle#134 Otherwise we need to do another iteration to update the plugin version to support parallel test execution @ThisaruGuruge @Thevakumar-Luheerathan WDYT?

That's better, I think. I'll release a gradle plugin with parallel test support before EOD.

[Thevakumar-Luheerathan]

A plugin version of v2.2.3 is released now. @TharmiganK @DimuthuMadushan please use that.