-
Notifications
You must be signed in to change notification settings - Fork 45
Description
How can Veracode srcclr be used in a modern gradle software build that uses build-logic/ to hold common logic used by all the components (libraries and apps) in a composite build?
For instance, with gradle 8.0.2 running % gradle init, picking application, Java, app & lib, Groovy, yes - using new APIs, creates pluginManagement { includeBuild('build-logic') } in settings.gradle.
dependencies { implementation 'gradle.plugin.com.srcclr:gradle:3.1.12' } can be added to build-logic/build.gradle; and id 'com.srcclr.gradle' to build-logic/src/main/groovy/myapp.java-common-conventions.gradle, along with srcclr { apiToken = '...' }`.
But running ./gradlew srcclr fails with:
Execution failed for task ':app:srcclrEvidence'.
> Resolving dependency configuration 'default' is not allowed as it is defined as 'canBeResolved=false'.
Instead, a resolvable ('canBeResolved=true') dependency configuration that extends 'default' should be resolved.
Can the srcclr gradle plugin be fixed to work in build-logic/, ie in a composite build?