Google Web Toolkit

Thursday, April 16, 2026

Re: Build warning

Thanks, I have created an issue for it: https://github.com/gwtproject/gwt/issues/10309

-- J.

Mirza Hadžič schrieb am Donnerstag, 16. April 2026 um 15:41:41 UTC+2:

Hi,

Java 26 with GWT 2.13 has this warnig:

WARNING: Final field map in class
com.google.gwt.thirdparty.guava.common.collect.ImmutableMultimap has
been mutated reflectively by class
com.google.gwt.thirdparty.guava.common.collect.Serialization$FieldSetter
in unnamed module @74e52303 (fi

Mirza

--
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/3b7b65b4-7857-4588-95ca-43109595d31bn%40googlegroups.com.

Hi, Java 26 with GWT 2.13 has this warnig: WARNING: Final field map in class com.google.gwt.thirdparty.guava.common.collect.ImmutableMultimap has been mutated reflectively by class com.google.gwt.thirdparty.guava.common.collect.Serialization$FieldSetter in unnamed module @74e52303 (fi Mirza -- 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/6501a164-70db-4666-9f5d-6c9e2a0a0709%40digitech.cz.

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.

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

Hi Thomas

Thank you for your hint, there was indeed a launcherDir in the root pom.xml (the -DLauncherDir was a typo in the message, not in the commande). Using -DlauncherDir works perfectly. I think I'll rely on properties with provided scripts to launch codeServer rather then execuitonsIds since this does the jobs and does not involve some strange Voodoo tricks :-)

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?

Kind regards

Le lundi 13 avril 2026 à 17:38:22 UTC+2, Thomas Broyer a écrit :

On Monday, April 13, 2026 at 1:58:41 PM UTC+2 beussl...@gmail.com wrote:

Hi group,
We've a pretty large multimodule projet which delivers two wars with different server code. One of the war includes 3 gwt apps and the other one 1 gwt app (4 applications total).

I was wondering if there was a way to configure a separate launcherDir for the fourth application. Given the fact that it's done in root pom I'm assuming I'll have to rely on properties but if there's a better way I'd be happy to use it

I think I would declare 2 <execution>s (one of them could use the default-cli executionId), each with its own <launcherDir>, and either <modules> or <projects>, and then run "mvn gwt:codeserver@foo" and "mvn gwt:codeserver@bar"

By the way, passing -DLauncherDir on the CLI does not seem to have any effect on the generated command line

Besides that it's -DlauncherDir rather than -DLauncherDir (lowercase L), that can only work if you do not have a <launcherDir> configured in your POM. You should be able to experiment with the above by removing most configuration in the root POM and then running "mvn gwt:codeserver -DlauncherDir=… -Dgwt.projects=…"

--
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/5f33ee79-faca-4810-a30f-9d257e2e7201n%40googlegroups.com.

Monday, April 13, 2026

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

On Monday, April 13, 2026 at 1:58:41 PM UTC+2 beussl...@gmail.com wrote:

Hi group,
We've a pretty large multimodule projet which delivers two wars with different server code. One of the war includes 3 gwt apps and the other one 1 gwt app (4 applications total).

I was wondering if there was a way to configure a separate launcherDir for the fourth application. Given the fact that it's done in root pom I'm assuming I'll have to rely on properties but if there's a better way I'd be happy to use it

I think I would declare 2 <execution>s (one of them could use the default-cli executionId), each with its own <launcherDir>, and either <modules> or <projects>, and then run "mvn gwt:codeserver@foo" and "mvn gwt:codeserver@bar"

By the way, passing -DLauncherDir on the CLI does not seem to have any effect on the generated command line

Besides that it's -DlauncherDir rather than -DLauncherDir (lowercase L), that can only work if you do not have a <launcherDir> configured in your POM. You should be able to experiment with the above by removing most configuration in the root POM and then running "mvn gwt:codeserver -DlauncherDir=… -Dgwt.projects=…"

--
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/00a727c6-7073-4c98-bc40-367e4d1651cdn%40googlegroups.com.

Per-module launcherDir using gwt-maven-plugin

Hi group,

We've a pretty large multimodule projet which delivers two wars with different server code. One of the war includes 3 gwt apps and the other one 1 gwt app (4 applications total).

I was wondering if there was a way to configure a separate launcherDir for the fourth application. Given the fact that it's done in root pom I'm assuming I'll have to rely on properties but if there's a better way I'd be happy to use it

By the way, passing -DLauncherDir on the CLI does not seem to have any effect on the generated command line

Kind regards

--
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/3efec5be-3a6c-435d-bb04-af8f3bcae1c1n%40googlegroups.com.

Thursday, March 26, 2026

Re: no gwt or static content included in app

finally found by lurking in the group questions.

in my Main html page, Module.html, had to add

for the

when I removed the folder in script tag, the nocache was not found and the meta is needed for other files listed in " Module.nocache.js" where the base folder was not there.

Le jeudi 26 mars 2026 à 16:06:07 UTC+1, Régis Millet a écrit :

Still no js found.
they are generated but not exploded.

Le jeudi 26 mars 2026 à 15:27:34 UTC+1, Régis Millet a écrit :
when i tried a lot of things , i "lost" my gwt-user dependency.
building currently running

Le jeu. 26 mars 2026 à 15:09, Régis Millet <mille...@gmail.com> a écrit :
OK, my understanding of the goals was wrong.

but now that I only put compile, I get - gwt-maven-plugin:1.2.0:compile (default) @ module ---
[INFO] Loading inherited module 'fr.company.module.Module'
[INFO] Loading inherited module 'com.google.gwt.core.Core'
[INFO] [ERROR] Unable to find 'com/google/gwt/core/Core.gwt.xml' on your classpath; could be a typo, or maybe you forgot to include a classpath entry for source?

Le jeudi 26 mars 2026 à 15:01:38 UTC+1, Thomas Broyer a écrit :
On Thursday, March 26, 2026 at 2:54:35 PM UTC+1 mille...@gmail.com wrote:

<executions>
<execution>
<goals>
<goal>generate-module</goal>
<goal>codeserver</goal>

</goals>
</execution>
</executions>
</plugin>

You don't GWT-compile your application, you need to call the "compile" goal here.

Also, it's weird and useless to have the codeserver goal here (weird because you wouldn't want to call it during a "standard" build, you want to explicitly invoke it from the command line, and useless because it doesn't bind to any lifecycle phase by default, so it won't be executed anyway without some more configuration)

--
You received this message because you are subscribed to a topic in the Google Groups "GWT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/07aw4tsunPE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-tool...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/77c94799-7c97-40c5-9bae-5e3aa43c8c83n%40googlegroups.com.

--
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/bbbe638c-1b71-4686-ad22-0c7ab585e281n%40googlegroups.com.