Skip to content
This repository has been archived by the owner on Jan 25, 2021. It is now read-only.

Multi-module project with flavors: module does not include other modules it depends on #79

Open
connected-kli opened this issue Nov 9, 2018 · 0 comments

Comments

@connected-kli
Copy link

Hi,

We have a multi-module project in which some modules depend on other modules. These modules also have flavors.

We followed the example in https://github.com/mirceanis/multi-flavor-lib-demo in order to get JitPack to properly publish the project's artifacts, and things are mostly working fine.

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant