Can you describe your project layout, how the modules are structured, 
depend on each other, how your source directories are laid out? What is the 
<packaging> of this client project where the pom is, and what command are 
you running to build (and from which directory)?

Consider downgrading to GWT 2.11 and only change the plugin, rather than 
changing both plugin and GWT version at the same time, so that you don't 
confuse issues from one change with the other.

Also consider using one of the archetypes to generate a sample project, and 
then look at the differences between your project and that sample. You can 
adjust the archetype-created project to be more like your own, and when it 
stops building, you may have a better idea about what is going on.

On Monday, November 11, 2024 at 3:12:47 PM UTC-6 [email protected] wrote:

>
> Thanks Frank to look into this.  Following is the entry in my pom.xml:
>
> <plugin>
>
> <groupId>net.ltgt.gwt.maven</groupId>
>
> <artifactId>gwt-maven-plugin</artifactId>
>
> <version>1.1.0</version>
>
> <executions>
>
> <execution>
>
> <goals>
>
> <goal>compile</goal>
>
> </goals>
>
> </execution>
>
> </executions>
>
> <configuration>
>
> <moduleName>com.medhok.mm.OEV</moduleName>
>
> <moduleShortName>MedicalMgmt</moduleShortName>
>
> <failOnError>true</failOnError>
>
> <!-- GWT compiler 2.8 and above requires 1.8, hence define sourceLevel 
> here if you use
>
> a different source language for java compilation -->
>
> <sourceLevel>1.8</sourceLevel>
>
> <!-- Compiler configuration -->
>
> <compilerArgs>
>
> <!-- Ask GWT to create the Story of Your Compile (SOYC) (gwt:compile) -->
>
> <arg>-compileReport</arg>
>
> <arg>-XcompilerMetrics</arg>
>
> </compilerArgs>
>
> <!-- DevMode configuration -->
>
> <warDir>${webappDirectory}</warDir>
>
> <classpathScope>compile+runtime</classpathScope>
>
> <!-- URL(s) that should be opened by DevMode (gwt:devmode). -->
>
> <startupUrls>
>
> <startupUrl>index.html</startupUrl>
>
> </startupUrls>
>
> </configuration>
>
> </plugin>
> As per entry in the plugin it has to look into src/main/java.  Some how 
> it's not finding the right classpath entry.
>
> Appreciate your help.
>
> On Monday, November 11, 2024 at 4:05:19 PM UTC-5 Venkateswara Rao wrote:
>
>> I have moved to src/main/java. Didn't rename.
>>
>> On Monday, November 11, 2024 at 4:01:23 PM UTC-5 Frank Hossfeld wrote:
>>
>>> Have you tried to move your OEV.gwt.xml  into the main folder and rename 
>>> it to: module.gwt.xml? 
>>>
>>> Venkateswara Rao schrieb am Montag, 11. November 2024 um 18:49:42 UTC+1:
>>>
>>>> Hello,
>>>>
>>>> Currently I am migration my gwt application from 2.11.0 to 2.12.0 with 
>>>> .  During this migration we are getting the following error:
>>>> [ERROR] Unable to find 'com/medhok/mm/OEV.gwt.xml' on your classpath; 
>>>> could be a typo, or maybe you forgot to include a classpath entry for 
>>>> source?
>>>> Any leads on this error.
>>>>
>>>> However, as part of the following article 
>>>> https://tbroyer.github.io/gwt-maven-plugin/ I have moved my src to 
>>>> src/main/java.
>>>>
>>>> Still I am getting the above error.
>>>>
>>>> Appreciate your help.
>>>>
>>>> Thanks,
>>>> Venkat.
>>>>
>>>

-- 
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/b68eb1e1-640d-4185-bc03-124b48c210e9n%40googlegroups.com.

Reply via email to