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

Allow more than one configuration #334

Open
rschnitk opened this issue Mar 29, 2023 · 0 comments
Open

Allow more than one configuration #334

rschnitk opened this issue Mar 29, 2023 · 0 comments

Comments

@rschnitk
Copy link

I'm not entirely sure, but I don't think it's currently possible to hold two configurations. Use case: one configuration for the CI run (with suppressions, CVE score = 0), another for the release (all findings, no suppression). You can partly use Gradle Properties, but that's not so nice, since the task may not be executed a second time.

Reason: the class ConfiguredTask only search for one 'dependencyCheck' definition.

Here is an example for the asciidoc plugin:

task asciidoctorTaskOne( type: org.asciidoctor.gradle.jvm.AsciidoctorTask ) {
key1 value1
key2 value2
}

task asciidoctorTaskTwo( type: org.asciidoctor.gradle.jvm.AsciidoctorTask ) {
key1 value3
key2 value4
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant