Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Library Dependencies Across Layers #163

Open
StuStirling opened this issue Jun 22, 2016 · 1 comment
Open

Library Dependencies Across Layers #163

StuStirling opened this issue Jun 22, 2016 · 1 comment

Comments

@StuStirling
Copy link

StuStirling commented Jun 22, 2016

I have a library module that I am reusing across multiple applications.

The library is composed of two modules. One android library module that depends on a java library module that contains my domain logic.

Then in the project that I depend on this library I have split into the three modules used in the Android-CleanArchitecture application.

My questions is:

How do I use objects from the domain module from my android library in the main project's domain module? At the moment I would have to convert the main project's domain module to an android library module.

At the moment, in the Android-CleanArchitecture application, it doesn't really use any reusable modules so I couldn't see how this would be done.

@android10
Copy link
Owner

Maybe you should go for One Module Clean Architecture approach. We have had discussions here, it is a PR and the idea is to not merge but keep it around: #103

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

No branches or pull requests

2 participants