Do a "gradle dependencies" from the command line to see all the project configurations to make sure the one you need is there.
On Mon, Mar 10, 2014 at 10:00 AM, Streets Of Boston <[email protected] > wrote: > I tried your suggestion, but i can't get it to work. > > I keep getting these type of error messages when syncing the gradle file > (envTest and Mediaarc are two flavors, Debug is the build type). > > I checked that 'envTestMediaarcDebug' is a proper build flavor. > > In build.gradle there is this line in the dependencies: > > envTestMediaarcDebugCompile project(path: > ':libraries:android-jenga-rest', configuration: 'mediaarcDebug') > > When syncing the build.gradle, it gives this error: > > Build script error, unsupported Gradle DSL method found: > 'envTestMediaarcDebugCompile()'! > > I tried with and without the 'Debug', i tried > 'compileEnvTestMediaarcDebug' instead, (with and without the 'Debug' > part)... > It always give the DSL method not found error. > > I probably do something wrong, but I can't figure out what.... > > > On Wednesday, March 5, 2014 4:04:38 PM UTC-5, Xavier Ducrohet wrote: > >> You could, but the dependencies are very manual for now. >> >> So in your apps you'd have to do something like this: >> >> dependencies { >> flavor1Compile project(path: ':lib1', configuration: 'flavor1Release') >> flavor2Compile project(path: ':lib1', configuration: 'flavor2Release') >> } >> >> This is really not great if you have a different flavor groups, but it's >> possible at least. >> >> >> On Wed, Mar 5, 2014 at 12:12 PM, Streets Of Boston >> <[email protected]>wrote: >> >>> Question about library build-variants with app build-variants. >>> >>> I have a number of apps with a number of build-variants (defined in >>> flavorGroups and productFlavors). >>> I have a library project supporting all these apps. >>> >>> The variant-sources in the apps redefine stuff (code/resources) that are >>> originally defined/declared in the library project. >>> These re-definitions are the same for each app, duplicated, because the >>> library project didn't support build-variants. >>> >>> Now that library projects support build-variants, is there a way to tie >>> an app's product-flavor to a library build-variant and move the >>> variant-sources from the app-projects to the variant-sources of the >>> library-project? >>> >>> Thanks! >>> >>> >>> On Wednesday, March 5, 2014 2:18:27 PM UTC-5, Xavier Ducrohet wrote: >>>> >>>> Release notes: http://tools.android.com/tech-docs/new-build-system >>>> >>>> -- >>>> Xavier Ducrohet >>>> Android SDK Tech Lead >>>> Google Inc. >>>> http://developer.android.com | http://tools.android.com >>>> >>>> Please do not send me questions directly. Thanks! >>>> >>> -- >>> 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. >>> >> >> >> >> -- >> Xavier Ducrohet >> Android SDK Tech Lead >> Google Inc. >> http://developer.android.com | http://tools.android.com >> >> Please do not send me questions directly. Thanks! >> > -- > 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/d/optout. > -- Xavier Ducrohet Android SDK Tech Lead Google Inc. http://developer.android.com | http://tools.android.com Please do not send me questions directly. Thanks! -- 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/d/optout.
