Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolving configuration 'generatedImplementation' directly is not allowed #10

Closed
jamestweeddale opened this issue Jul 29, 2019 · 2 comments

Comments

@jamestweeddale
Copy link

cyclonedxBom task runs but eventually fails with error "Resolving configuration 'generatedImplementation' directly is not allowed". Also seeing many "Unable to resolve POM for..." errors

Task :cyclonedxBom FAILED
:cyclonedxBom (Thread[Daemon worker,5,main]) completed. Took 1 mins 58.585 secs.

FAILURE: Build failed with an exception.

  • What went wrong:
    Execution failed for task ':cyclonedxBom'.

Resolving configuration 'generatedImplementation' directly is not allowed

  • Try:
    Run with --stacktrace option to get the stack trace. Run with --debug option to get more log output. Run with --scan to get full insights.

  • Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 6.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/5.4.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 2m 5s
1 actionable task: 1 executed

stefanneuhaus added a commit to stefanneuhaus/cyclonedx-gradle-plugin that referenced this issue Aug 5, 2019
… directly is not allowed

Check for resolvability of configurations first
stefanneuhaus added a commit to stefanneuhaus/cyclonedx-gradle-plugin that referenced this issue Aug 5, 2019
… directly is not allowed

Check for resolvability of configurations first
@sschuberth
Copy link
Contributor

@stevespringett, mind closing this, too, now that version 1.1.1 is released?

@lock
Copy link

lock bot commented Oct 3, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Oct 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants