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
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?
The text was updated successfully, but these errors were encountered:
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.
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?
The text was updated successfully, but these errors were encountered: