Tuesday, April 14, 2026

Re: Per-module launcherDir using gwt-maven-plugin



On Tuesday, April 14, 2026 at 10:18:49 AM UTC+2 beussl...@gmail.com wrote:
Also I've a question wrt plugin usage, it looks like if I've A → B → C dependencies with A & B being gwt-lib-packaged and C gwt-app, I have to declare A as regular and classifier:sources dependency in B in order for A to be correctly picked up when launching codeServer on C, using <type>gwt-lib</type> on transitive dependencies does not seem to work as sources are not found. Did I, again, miss something?

AFAIR, this should work.
It seems to work within the https://github.com/tbroyer/gwt-maven-plugin/tree/main/src/it/e2e integration test (clone the repo, checkout the 1.2.0 tag, run mvn clean verify, go to target/it-tests/e2e, run mvn gwt:codeserver -X, notice that it does print some ignored dependencies –due to the way projects are setup, but this might also not trigger the issue–, but the -src in the arguments are OK, then call http://127.0.0.1:9876/recompile/e2e?user.agent=safari to trigger a compilation and all goes well; this can be checked by opening http://127.0.0.1:9876/e2e/ in a browser)

Can you create a repro and open an issue?
(feel free to use the e2e integration test as a starting point, at least regarding the Java/GWT code)

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/1e54365f-9e7a-447c-a380-6be3a8dca6a0n%40googlegroups.com.

No comments:

Post a Comment