CycloneDX / CycloneDX/cyclonedx-gradle-plugin
Spring/Scala project: No matching variant of XXX was found.
- Dominant language
- Java
- Stars
- 239
- Forks
- 102
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 11
Description
Trying to add cycloneDX to an existing Gradle project. `./gradlew cyclonedxBom` produces a ton of errors of the form:
```
Could not resolve XXX.
Required by:
project :
> No matching variant of XXX was found. The consumer was configured to find a usage of 'incremental-analysis' of a component but:
- Variant 'compile' XXX:
- Incompatible because this component declares an API of a component and the consumer needed a usage of 'incremental-analysis' of a component
- Variant 'enforced-platform-compile' capability XXX:
- Incompatible because this component declares an API of a component and the consumer needed a usage of 'incremental-analysis' of a component
- Variant 'enforced-platform-runtime' capability XXX:
- Incompatible because this component declares a runtime of a component and the consumer needed a usage of 'incremental-analysis' of a component
- Variant 'platform-compile' XXX:
- Incompatible because this component declares an API of a component and the consumer needed a usage of 'incremental-analysis' of a component
- Variant 'platform-runtime' capability XXX
- Incompatible because this component declares a runtime of a component and the consumer needed a usage of 'incremental-analysis' of a component
- Variant 'runtime' capability XXX:
- Incompatible because this component declares a runtime of a component and the consumer needed a usage of 'incremental-analysis' of a component
```
Not sure what to do here, don't work with these types of projects real often
Contributor guide
Research direction
Start by reproducing the reported failure with `./gradlew cyclonedxBom` in the existing Spring/Scala Gradle project described in the issue. Inspect the dependency-resolution output and project configuration to identify why the consumer requests `incremental-analysis`; done means the task completes without the reported no-matching-variant errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, scala, spring
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100