This indeed seems to be what I was looking for, thank you.
Are there any obvious downsides to doing it like this, with multiple 
executions?

Does it matter which specific moduleName I specify within the 
<configuration> tag, or should I just pick 1 arbitrary one there and put 
the others within the <executions> tag?

I very much appreciate the responses and the patience ;)

On Tuesday, May 9, 2017 at 12:22:40 PM UTC+2, Thomas Broyer wrote:
>
>
>
> On Tuesday, May 9, 2017 at 11:27:25 AM UTC+2, Frederik Van Hoyweghen wrote:
>>
>> Thanks for the replies.
>>
>> I already took a look at the issue on the plugin's github: 
>> https://github.com/tbroyer/gwt-maven-plugin/issues/57 
>> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Ftbroyer%2Fgwt-maven-plugin%2Fissues%2F57&sa=D&sntz=1&usg=AFQjCNF_nWBU0PRbRDsCHtnr5SjxFJNUwQ>
>> Sadly, this was closed and recently labeled with a wontfix, hence me 
>> asking for help here :)
>>
>
> My first comment on this issue tells you how to do it. In case it isn't 
> clear, what I meant there is:
>
> <executions>
>   <execution>
>     <id>compile-module1</id>
>     <goals>
>       <goal>compile</goal>
>     </goals>
>     <configuration>
>       <moduleName>com.example.module1.Module1</moduleName>
>       <moduleShortName>module1</moduleShortName>
>     </configuration>
>   </execution>
>   <execution>
>     <id>compile-module1</id>
>     <goals>
>       <goal>compile</goal>
>     </goals>
>     <configuration>
>       <moduleName>com.example.module2.Module2</moduleName>
>       <moduleShortName>module2</moduleShortName>
>     </configuration>
>   </execution>
> </executions>
>
> Another possibility (if you really do want to fork one and only one GWT 
> compiler process) is to use the exec-maven-plugin's exec goal (though you 
> would have to declare your source roots as resources dirs to get your 
> sources copied to target/classes so they're present in the computed 
> <classpath/>).
> (I suppose you could get something working by "hacking" into the 
> <compilerArgs>, and probably then <forceCompilation>true</forceCompilation> 
> as you'd have the staleness check only take the module configured in 
> <moduleName>/<moduleShortName> into account; I would discourage such "hack" 
> though)
>

-- 
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to