[Regression in 0.7] Unable to resolve configuration :runtime about gradle-license-report HOT 7 CLOSED

👍 Upgrading to Gradle 4.6 resolved the issue. Thanks! Marking issue as Closed.

( Note: I did run into another issue with the XML renderer, but will file a separate ticket for that. )

from gradle-license-report.

Hm, that's unfortunate. Can you post your licenseReport configuration of your gradle-file?

I tested the latest version, and runtime works for me.

Only problem can be, that runtime might not be available on your project. Can you execute

./gradlew dependencies

to see if the configuration runtime is available? Actually, the 0.7 release made a check a little more restrictive, to avoid specifying configurations, which are not available. This is maybe the case here.

from gradle-license-report.

There's no licenseReport section in my Gradle file.

Here's the output from gradle dependencies (with some identifiers masked):
dependencies.txt

Notice that runtime does show up:

runtime - Runtime dependencies for source set 'main'.
+--- com.*****.apex:*****client:1.3.0
|    \--- com.*****.apex:web:3.4.0 -> 3.19.0
|         +--- commons-codec:commons-codec:1.10
|         +--- com.*****.apex:auth:3.0.0

from gradle-license-report.

Thanks for the report. It seems that the PR broke support for older versions of Gradle. Versions from 3.3 seems to work fine. Version below, have problems.
You use version 2.13. Upgrading to version 3.3 or later will solve your problem.

@jk1 Do you tend to be backward compatible with those older versions (Release Date of 3.3. was Jan 03, 2017), or do you prefer adding a minimum required version to the documentation?

I personally like to motivate people to be up to date with their build tool, in order to use all the plugins and feature, so I tend to break compatibility with versions lower than 3.3.

@znerd Is upgrading to a new version an option?

from gradle-license-report.

@guenhter

I personally like to motivate people to be up to date with their build tool, in order to use all the plugins and feature, so I tend to break compatibility with versions lower than 3.3.

So am I. We'd better check Gradle version in Plugin#apply(...) though and print out an explanatory message to avoid confusion. Something like

    private void assertCompatibleGradleVersion() {
        def current = GradleVersion.current().version.split("\\.")
        def major = current[0].toInteger()
        if (major < 4) {
            throw new GradleException("License Report Plugin requires Gradle 4.0. ${GradleVersion.current()} detected.")
        }
    }

will do.

from gradle-license-report.

@guenhter Thanks for the swift analysis.

I fully understand it makes sense to stay up-to-date with regards to the current build tool version.

from gradle-license-report.

Even though upgrading solved the Problem, #62 added a version check which gives a proper message when using this plugin with an outdated gradle-version.

from gradle-license-report.