Per-module launcherDir using gwt-maven-plugin

[Sébastien]

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

[Thomas Broyer]

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=…"