Folder path about gradle-play-publisher

[bhurling]

Can you explain why you are overriding the default source sets? Do you have multiple customers, where each customer has those two flavors? That would be exactly what flavor dimensions are for.

I could, however, think of a solution where we extend the sourceSets DSL. Something like:

sourceSets {
        flavor1 {
            res.srcDir  'src/main/adhocs/flavor1/res'
            assets.srcDir 'src/main/adhocs/flavor1/assets'
            play.srcDir 'src/main/adhocs/flavor1/play'
        }

        flavor2 {
            res.srcDir  'src/main/adhocs/flavor2/res'
            assets.srcDir 'src/main/adhocs/flavor2/assets'
            play.srcDir 'src/main/adhocs/flavor1/play'
        }
}

But that seems a little ambitious and I don't see the real benefit for now.

[bhurling]

Isn't your customer a flavor dimension on its own? If so, files in src/${customer}/${flavorDimension2}/play should already be packaged correctly.

[xjrcode]

I do not use flavorDimension, only productFlavors like:

productFlavors {
        flavor1 {
            packageName "com.example.flavor1"
            versionCode 20
        }

        flavor2 {
            packageName "com.example.flavor2"
            minSdkVersion 14
        }
}

sourceSets {
        flavor1 {
            res.srcDir  'src/main/adhocs/flavor1/res'
            assets.srcDir 'src/main/adhocs/flavor1/assets'
        }

        flavor2 {
            res.srcDir  'src/main/adhocs/flavor2/res'
            assets.srcDir 'src/main/adhocs/flavor2/assets'
        }
}

[xjrcode]

We have a base app fully customizable. We make one flavor for each customer with its own assets folder.

Your solution is perfect for these cases, as each customer has his own google play info.

[SUPERCILEX]

Since the solution above works and changing source sets is unconventional, the original feature request is no longer needed.