build.gradle
files. As the only truly reliable way to resolve Gradle dependencies is to execute the tool itself, this method can sometimes provide incomplete results.3.*
2.*
, 3.*
,4.*
, 5.*
, 6.*
build.gradle
and build.gradle.kts
pom.xml
files.--sub-project=
--all-sub-projects
--configuration-matching=
'^releaseRuntimeClasspath#x27;
--configuration-attributes=
'buildtype:release,usage:java-runtime'
--all-projects
--all-sub-projects
behind the scenes. This command is designed to be run in the root of your monorepo.settings.gradle
file. Sub-projects depend on the root project, but can be configured otherwise.--file=path/to/build.gradle
).--all-sub-projects
flag:--configuration-matching
option with a Java regular expression (case-insensitive) as its parameter. The configuration that matches is then tested. If several configurations match, they are all merged and resolved together. For example: '^releaseRuntimeClasspath$|^compile#x27;
--configuration-matching=compile
will match compile, testCompile, compileOnly etc;--configuration-matching=^compile$
will match only compile;--configuration-matching='^(debug|release)compile#x27;
will match debugCompile and releaseCompile--configuration-matching='^(?!.*lintClassPath).*#x27;
will match all configurations except lintClassPathproject :mymodulewithvariants
project :mymodulewithvariants
com.android.build.api.attributes.BuildTypeAttr=release
and org.gradle.usage=java-runtime
gradle build --no-daemon
in the background when running snyk test
and snyk monitor
. If for any reason, you run into trouble, try this:--daemon
to your snyk test
or snyk monitor
.<
[email protected]
>
so we can help you out:build.gradle
settings.gradle
(especially if we did not pick up a version of a package)$ snyk test -d
$ gradle dependencies -q
pom.xml
file.build.gradle
file and (optional) gradle.lockfile
.build.gradle.kts
files are not currently supported in Git.