You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I work on a large multi-project Gradle build and there are some Scala subprojects where Scoverage is intentionally not applied, e.g. API modules. This results in many warnings (36 in our case) being logged during configuration, before every gradle command is executed.
It would be nice to have a way to exclude subprojects individually from the parent project aggregation so this warning is skipped, or to have some other way to avoid the warning e.g. suppressing it generally with a Boolean option on the parent project.
The configuration for this could look something like:
I work on a large multi-project Gradle build and there are some Scala subprojects where Scoverage is intentionally not applied, e.g. API modules. This results in many warnings (36 in our case) being logged during configuration, before every gradle command is executed.
It would be nice to have a way to exclude subprojects individually from the parent project aggregation so this warning is skipped, or to have some other way to avoid the warning e.g. suppressing it generally with a Boolean option on the parent project.
The configuration for this could look something like:
The text was updated successfully, but these errors were encountered: