Skip to content

Conversation

@sebastienrouif
Copy link

Added the option to test flavoured android modules thanks to testedFlavourName parameter
it would solve #24

public var additionalSourceSets: MutableSet<String> = HashSet()

/**
* In Android projects with multiple flavour,

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo: flavours

* Copyright 2016-2022 JetBrains s.r.o.
* Use of this source code is governed by the Apache 2.0 License that can be found in the LICENSE.txt file.
*/
import org.jetbrains.kotlin.gradle.plugin.*

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nitpick: Should it follow the same rules as in other changed files for explicit imports? Or vice versa?

@GokhanArik
Copy link

@qwwdfsad Is it possible to prioritise this PR?

@NMGuner
Copy link

NMGuner commented Oct 19, 2023

Does this take into account that some modules inside the project might lack flavors or the particular flavor set here?(when the plugin is configured in the root gradle file) My suggestion would be to generate unique tasks for each flavor, similar to other gradle plugins compatible with flavors.

@sebastienrouif
Copy link
Author

Fair, I don't think I have checked that, let's try

@shanshin
Copy link
Contributor

As part of the migration of separate BCV functionality to Kotlin Gradle Plugin, the addition of new features to a separate plugin has been discontinued.

@shanshin shanshin closed this Jun 16, 2025
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

Successfully merging this pull request may close these issues.

5 participants