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

Support for multimodule project #15

Open
shabunc opened this issue Jan 7, 2018 · 2 comments
Open

Support for multimodule project #15

shabunc opened this issue Jan 7, 2018 · 2 comments

Comments

@shabunc
Copy link

shabunc commented Jan 7, 2018

In the project from which one this particular project has been forked there was an issue with supporting multimodule gwt project (one where something in *.gwt.xml declaration inherits from different module).

up to that moment there was no solution other then explicitly add all gwt dependencies to the classpath which is non-ideal solution because it's defied the sole purpose of declaring dependencies.

just wonder has anything changed since then regarding this particular problem?

@jiakuan
Copy link
Owner

jiakuan commented Jan 8, 2018

No I don’t think there are any changes in this regard.

In Gradle multiple-project structure, I normally use the project dependency configuration and didn’t see any problems. Perhaps I didn’t understand this issue properly.

Is there a sample project to play with?

@gkresic
Copy link

gkresic commented Jul 18, 2018

Maybe at least add to examples that equivalent of

evaluationDependsOn(':example-library')

is required in top level project, or otherwise gwt declaration won't be evaluated properly. @shabunc mentioned that in comment on above issue.

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

No branches or pull requests

3 participants