Question: Codeserver dependency problem when using multiple GWT modules about gwt-maven-plugin HOT 3 CLOSED

@tbroyer Wondering if you could have a look at this. Most likely something in my config is wrong. Is there a sample project with multiple gwt-app packaged Maven modules anywhere?

from gwt-maven-plugin.

Could it be that you are sharing the same package/subpackage between projects?

There's no gwt-app isolation with SDM when using it with multiple modules/projects at once, contrary to gwt:compile for instance.

If com.xxxx.frame.client.Portal is in the client-path of Module 2 (or one of its dependencies), then GWT will check it when compiling Module 2.

Solutions are:

• either using skip=""/<skip> in Module 2 (undocumented, but works similarly to include/exclude: http://www.gwtproject.org/doc/latest/DevGuideOrganizingProjects.html#DevGuidePathFiltering; difference with exclude is that you could skip a source in one GWT module but have another GWT module include it; whereas exclude will completely exclude it from the client-path, and no other GWT module can include it)
• or move files around / rename packages to avoid such conflicts
• or run several distinct gwt:codeserver (with -Dgwt.modules= or -Dgwt.projects=, or using distinct <execution>s each with their own <configuration> and invoking them by their ID on the commande line: https://maven.apache.org/docs/3.3.1/release-notes.html#plugin-goal-invocation-from-command-line)

from gwt-maven-plugin.

Thanks for looking into this @tbroyer .

There are overlaps in the client-paths and I will first see to eliminate them. Thanks for the other options, I'll give these a try over the next days.

Are you aware of any (sample) Maven setups which use multiple GWT module to implement the old "GWT Turducken" pattern, i.e. multiple independent GWT modules?

from gwt-maven-plugin.