I'm afraid you're not providing enough information for us to help.

First, I'm assuming you 
read https://tbroyer.github.io/gwt-maven-plugin/migrating.html, as well 
as https://tbroyer.github.io/gwt-maven-plugin/index.html 
and https://tbroyer.github.io/gwt-maven-plugin/usage.html. If you haven't 
already, I'd suggest studying the structure of a project generated from the 
gwt-maven-archetypes: https://github.com/tbroyer/gwt-maven-archetypes/ or 
the e2e project used in tests 
(https://github.com/tbroyer/gwt-maven-plugin/tree/main/src/it/e2e)

How's your code organized in your project? Is the client code in a separate 
project from the server code? Or both in the same project?
How did you configure the net.ltgt.gwt.maven:gwt-maven-plugin? How was the 
CodeHaus Mojo plugin configured?

You're mentioning src/main/java in the structure of "Third-Party JAR (T1)", 
does it mean it's a project in the same Maven reactor build? Or is it 
really a third-party JAR and it actually doesn't have a src/main/java?

The best way to troubleshoot is to run with debug logs (mvn -X) and look 
for two lines starting with "Classpath:" and "Arguments:" respectively. You 
can also compare their content vs. the content of the two lines starting 
with "Execute command" and "With CLASSPATH" emitted by the CodeHaus Mojo 
plugin in the debug logs.


On Sunday, November 23, 2025 at 7:07:47 PM UTC+1 Ism wrote:

> Request for Help: Migrating GWT 2.8.2 → 2.12.2 (Plugin + Version)
>
> We are in the process of migrating our project from *GWT 2.8.2* to *GWT 
> 2.12.2*, including switching from the old Mojo plugin to the new tbroyer 
> gwt-maven-plugin.
>
>    - 
>    
>    With *GWT 2.8.2 + Mojo plugin*, everything has worked fine for several 
>    years.
>    - 
>    
>    After configuring the new plugin, we are running into issues.
>    
> Project Structure
>
> *Main Application Module* com.test.Application.gwt.xml
>
> This module inherits third-party JARs that contain both sources and their 
> own .gwt.xml files:
>
> <module> <inherits name="com.thirdparty.T1"/> </module> 
>
> *Third-Party JAR (T1)* Structure:
> Code
> src/main/java 
>  └── com/thirdparty/... 
>               └── T1.gwt.xml 
>
> Contents of T1.gwt.xml:
>
> <module> <source path=""/> </module> 
>
> *Problem*
>
> When migrating, compilation fails with:
> Code
> [ERROR] Line 40: No source code is available 
>
> Attempts so far:
>
>    - 
>    
>    Tried <source path=""/>
>    - 
>    
>    Tried <super-source path=""/>
>    
> Both approaches fail with the same error.
> Question
>
> How should we correctly configure the *tbroyer gwt-maven-plugin* and 
> module definitions so that third-party JARs with embedded sources and 
> .gwt.xml files are properly recognized under GWT 2.12.2?
>

-- 
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 view this discussion visit 
https://groups.google.com/d/msgid/google-web-toolkit/da5d1dc6-cc42-4d10-8071-d91a1124dc98n%40googlegroups.com.

Reply via email to