-
Notifications
You must be signed in to change notification settings - Fork 52
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
Explicitly included sourceSets (whitelist) #714
Labels
Comments
SIMULATAN
added
Feature
Feature request issue type
S: untriaged
Status: issue reported but unprocessed
labels
Dec 15, 2024
shanshin
added
S: postponed
Status: work on the issue is not in the short term plans
and removed
S: untriaged
Status: issue reported but unprocessed
labels
Dec 18, 2024
Thanks for the suggestion! This offer is definitely worth considering |
shanshin
added a commit
that referenced
this issue
Jan 7, 2025
shanshin
added a commit
that referenced
this issue
Jan 7, 2025
shanshin
added
S: ready for release
Status: merged in the main branch
and removed
S: postponed
Status: work on the issue is not in the short term plans
labels
Jan 8, 2025
Implemented in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
What is your use-case and why do you need this feature?
In my project, there's multiple test and development source sets, like
testIntegration
anddev
(for dev environment setup code). Manually excluding all of them without overlooking ones is a pain. This is further amplified by the fact that thetestIntegration
source set is added using aJvmTestSuite
convention that is only applied after Kover, therefore requiring the use ofafterEvaluate
in order to actually catch all non-main source sets.Describe the solution you'd like
Instead of just getting
excludedSourceSets
(aka "blacklist"), I'd like to have a "whitelist" approach as well. This way, I can only include themain
source set and don't have to worry about the initialization order, dev source sets, ...The text was updated successfully, but these errors were encountered: