I missed the part about registering the source folders. Shouldn't you need the artifact first to then associate the folders to that artifact?
For example lets say I have 4 flavors divided in two flavor groups, Free, Paid and Beta, Normal. so the normal structure for this would be: src - main - free - paid - beta - normal But then my plugin adds the following source directories (can be empty): src - test (main equivalent) - testDebug (for tests that need to be under debug) - testFree (flavor 1) - testFreeBeta (for variant) - testFreeDebug (For test that need to be both in debug and for flavor 1) - testFreeBetaDebug (the combination of variant and build type) - ... and so on for the rest of the combinations. But obviously only a task for variant and build type is made. so if i run check, it will run testFreeBetaDebug, testFreeNormalDebug, testPaidBetaDebug and testPaidNormalDebug (I ignore release build by default since debug should be enough). So each of this tasks will have as source set a combination of dirs. My idea would be to define only 4 extra artifacts but each artifact gets the right combination. For example: testFreeBetaDebug should have as sourceSet: "src/test;src/testFree;src/testDebug;src/testBeta;src/testFreeBeta;src/testFreeDebug;src/testBetaDebug;src/testFreeBetaDebug" so how exactly do I build a artifact with these folders?. -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
