On Sunday, July 10, 2022 at 6:03:14 AM UTC+2 [email protected] wrote:

> Hi folks,
>
> I'm moving away from the 'classic' Maven GWT plugin to net.ltgt.gwt.maven 
> by Thomas Broyer and I'm unclear to make client tests work. I created the 
> project using
>
> mvn archetype:generate    -DarchetypeGroupId=net.ltgt.gwt.archetypes    
> -DarchetypeVersion=LATEST    -DarchetypeArtifactId=modular-webapp
>
> modular-webapp doesn't generate client/test, so I just added standard 
> Maven structure using client/test/java, but those are not invoked.
>

Do you have GWTTestSuite matching the default *includes* 
<https://tbroyer.github.io/gwt-maven-plugin/test-mojo.html#includes>
 pattern?
If not, then either add one or change the includes to match your test 
classes (e.g. **/*Test.java, or the whole list from the default 
maven-surefire-plugin's value 
<https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#includes>
)
 

>
> https://tbroyer.github.io/gwt-maven-plugin/test-mojo.html speaks in terms 
> of proect base directories instead of the client module. Quote:
>
> ${project.build.directory}/gwt-tests/deploy.
>

Multi-modules in Maven are an after-thought, so $project always refers to 
the current *module* in a multi-module build. This means that 
${project.build.directory} defaults to the target/ directory inside your 
client module.

-- 
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 on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/97995833-bf87-4b32-95e8-9651ae980963n%40googlegroups.com.

Reply via email to