"Module has no entry points defined", except it does (migrating the gwt-maven-plugin)-CodePudding

[INFO] [ERROR] Module has no entry points defined

I am migrating from org.codehaus.mojo:gwt-maven-plugin to net.ltgt.gwt.maven:gwt-maven-plugin, and I can't seem to convince the compiler that my module DOES have an entry point defined.

The old plugin could only work with older Java, which I don't have anymore... So I moved on to the newer incarnation of the GWT Maven plugin... Unfortunately this plugin uses parameters that GWT 2.0.2 compiler does not recognize (like -deploy or -sourceLevel)... Which forced me to change ${gwt.version} to 2.8.2. That's rather massive jump, but I don't see how that could invalidate something as simple as implementing the EntryPoint interface.

TheApp/Web/src/main/module.xml:

    <entry-point class='net.theapp.client.TheEntryPoint' />
...
    <source path='net/theapp/client'/>
    <source path='net/theapp/data'/>

Location of the entry-point class:

TheApp/Web/src/main/java/net/theapp/client/
  - TheEntryPoint.java

The class:

...
public class TheEntryPoint
    implements EntryPoint
{
...

CodePudding user response：

You have named your module file module.mxl. The correct name is module.gwt.xml