You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 25, 2021. It is now read-only.
However, we found the following issue. Let's say :moduleA depends on :moduleB (via api project(:moduleB)), and both modules have flavors. The POM for :moduleA does not include :moduleB, which means consumers will have to know to add :moduleB as a dependency in their project. This makes consuming our library cumbersome.
This issue does not occur if we do not have flavors in both modules (and thus we can revert the change we learned from multi-flavor-lib-demo).
Is there a way to get :moduleA's POM to include :moduleB's artifacts?
Thanks in advance.
Odhita-Kamayana-ConnectedLab, franmaronas, UFreedom, alzhuravlev and droplet-js