embedRelease or embedDebug buildType or productFlavours support

[mochadwi]

Does it currently support different both buildTypes & productFlavours? @kezong

[kezong]

Flavor is supported, you can build in assembleFlavorRelease or assembleFlavor2Debug, but for the time it is not supported to write like
flavorEmbed 'com.facebook.fresco:fresco:1.11.0'

[mochadwi]

I see, awesome. But like you stated above, currently, we can't use buildTypes or buildFlavours for embed keywords.

With the general assemble[WithFlavour&BuildType] the aar merging can't be processed, right?

@kezong

EDITED:
With the general embed[WithFlavour&BuildType] the aar merging can't be processed, right?

[kezong]

With the general assemble[WithFlavour&BuildType], aar can be merged, and it is merged according to the customized of flavor & build type of each module.

[mochadwi]

My apologies look like I've been mistaken.

What I mean was, e.g:
embedDebug example:library:1.0.0-debug

Flavor is supported, you can build in assembleFlavorRelease or assembleFlavor2Debug, but for the time it is not supported to write like
flavorEmbed 'com.facebook.fresco:fresco:1.11.0'

As stated in your statement above. So the workaround will be using traditional approach e.g:
implementationDebug example:library:1.0.0-debug or

implementationRelease example:library:1.0.0-debug

Instead of embed when using implementation does the aar merging process skipped for that library? @kezong

[kezong]

Sorry, I don't quite understand.
Do you mean debugImplementation or releaseImplementaion ?
For the time debugEmbed or releaseEmbed is not supported, if you write like this, will resulting a compile error.

[mochadwi]

Sorry, I don't quite understand.

Yes, sorry for the typo.

Do you mean debugImplementation or releaseImplementaion ?

What I mean was [debug|release]Implementation

For the time debugEmbed or releaseEmbed is not supported, if you write like this, will resulting a compile error.

roger that.

[JirkaKrivanek]

Sorry, I am reading this thread third time and I am still confused, that is why I am trying to comment on it again...

Currently I have this in my gradle.build:

    debugImplementation 'com.gemalto.android.lib:http-real-debug:2.0.2'
    releaseImplementation 'com.gemalto.android.lib:http-real-release:2.0.2'

It is a MUST to have different dependency for debug resp. release (because the debug variant allows insecure HTTP connections while the release variant crashes on it).

Unfortunately, the http dependency is not embedded with the output AAR.

I would expect to be able to do something like this:

    debugEmbed 'com.gemalto.android.lib:http-real-debug:2.0.2'
    releaseEmbed 'com.gemalto.android.lib:http-real-release:2.0.2'

I already know that the intuitive way above does not work :)

From the thread above, I have a feeling that it actually is possible to achieve the effect somehow.

Could you please write a clear example for me?

[mochadwi]

No, it still not supported currently @JirkaKrivanek

[NMGuner]

Proposed a solution on #135 for build types and product flavors (only with single flavor dimension).