Resolving configuration 'implementation' directly is not allowed

[moritzhartmeier]

trafficstars

Hi,

We're using the plugin for the dependency license reporting, however, using version 0.14.0 with the following settings:

downloadLicenses {
    includeProjectDependencies = true
    dependencyConfiguration = 'implementation'
}

results in:

* What went wrong:
Execution failed for task ':base:downloadLicenses'.
> Resolving configuration 'implementation' directly is not allowed

It seems like this was brought up and fixed in #149 before (maybe for other parts of the code?) as it doesn't seem to work in the most recent version. Anything that can be done here?

[phekmat]

It looks like there hasn't been a release to capture that fix. 0.14.0 is over a year old at this point and the fix was merged a few months ago.

[hierynomus]

Yes, i still need to do this. Will try to remember coming week!

Op vr 1 jun. 2018 20:54 schreef Payam Hekmat [email protected]:

It looks like there hasn't been a release to capture that fix. 0.14.0 is over a year old at this point and the fix was merged a few months ago.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/hierynomus/license-gradle-plugin/issues/156#issuecomment-393977375, or mute the thread https://github.com/notifications/unsubscribe-auth/AAHLo1S3Qi6SETS5jC503sOKKKC6481Xks5t4Y3ugaJpZM4Tl8qE .

[philipphager]

Any updates on this ticket? It would be very helpful for our team to be able to use the implementation configuration.

[moritzhartmeier]

It's been another few months, a new release would be great

[Zudoku]

Any updates? This is making the feature completely unusable soon.

Configuration 'compile' is obsolete and has been replaced with 'implementation' and 'api'.
It will be removed at the end of 2018.

[hierynomus]

Can you try v0.15.0? Just released this.

[Pezzah]

I have also had problems getting this to work with the "implementation" configuration.

It looks like it is possible to force the configuration to be resolvable so the work around I have found is to define another task like:

downloadLicenses {
    dependencyConfiguration = 'implementation'
}

task myDownloadLicenses {
    finalizedBy "downloadLicenses"

    doFirst {
        project.configurations.getByName("implementation").setCanBeResolved(true)
    }
}

and then call myDownloadLicenses instead.