added a comment - - edited
This fix prevents a target module from being compiled when the target module extends another with an entry point. We use this scenario to only compile for a single target browser during development. For example, we have a gwt.xml that looks like this:
MyModule.gwt.xml
<module>
<entry-point class="com.mycompany.MyModule"/>
</module>
Then another gwt.xml that extends the one above that looks like this:
MyModuleFirefox.gwt.xml
<module>
<inherits name="com.mycompany.MyModule"/>
<set-property name="user.agent" value="gecko1_8" />
</module>
Previous to gwt-maven-plugin 1.2-SNAPSHOT we were able to point to MyModuleFirefox.gwt.xml and get a successful compile. With 1.2-SNAPSHOT, it skips the compilation because it doesn't find an entry-point in MyModuleFirefox.gwt.xml.
I confirmed this by commenting out the following if block in CompileMojo.compilationRequired().
if ( gwtModule.getEntryPoints().length == 0 )
{
return false;
}
The gwt-maven-plugin configuration for this build looks like the following, where the property gwt.module is set to MyModuleFirefox.gwt.xml:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>gwt-maven-plugin</artifactId>
<version>${gwt.plugin.version}</version>
<configuration>
<modules>
<module>${gwt.module}</module>
</modules>
<webappDirectory>${war.build.dir}</webappDirectory>
<runTarget>${gwt.run.target}</runTarget>
<style>PRETTY</style>
<noServer>${gwt.noserver}</noServer>
<jvm>${env.JVM_32BIT}</jvm>
<extraJvmArgs>${gwt.extra.jvm.args}</extraJvmArgs>
<debugPort>${gwt.debug.port}</debugPort>
<debugSuspend>${gwt.debug.suspend}</debugSuspend>
<whitelist>${gwt.run.target}</whitelist>
</configuration>
</plugin>
Wish
Closed
Major
This message is not generated by the plugin but by the compiler.
You certainly try to compile your project but did not specify the set of modules in plugin configuration.