Can't find gwt inherits

[tbroyer]

Can't find gwt inherits

[branflake2267]

I noticed your module.gwt.xml is not in the normal directory I would expect it. I've got mine in the source folder, would that make a difference? If I could see the command line output, I think that would help me understand the working args and help drill it.

https://github.com/branflake2267/Archetypes/tree/master/archetypes/gwt-basic/src/main/java/org/gonevertical/project - my module file

[branflake2267]

Looks like it's the gwt dependency scope, can't be provided. Commenting out fixes it... Hm.

[branflake2267]

Nevermind that wasn't it, I was running the code server.

[branflake2267]

mvn gwt:compile looks like this with the PR I pulled. This has the command line execution.

^CBrandons-MacBook-Pro:gwt-basic branflake2267$ mvn gwt:compile
[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building gwt-basic 2.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- gwt-maven-plugin:1.0-SNAPSHOT:compile (default-cli) @ gwt-basic ---
[INFO] Executing: /bin/sh -c cd '/Users/branflake2267/git/Archetypes/archetypes/gwt-basic/target' && '/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre/bin/java' 'com.google.gwt.dev.Compiler' '-logLevel' 'INFO' '-war' '/Users/branflake2267/git/Archetypes/archetypes/gwt-basic/target/gwt-basic-2.0-SNAPSHOT' '-workDir' '/Users/branflake2267/git/Archetypes/archetypes/gwt-basic/target/gwt/work' '-deploy' '/Users/branflake2267/git/Archetypes/archetypes/gwt-basic/target/gwt/deploy' '-style' 'OBFUSCATED' '-localWorkers' '8' '-optimize' '9' 'org.gonevertical.project.Project'
[INFO] Compiling module org.gonevertical.project.Project
[INFO]    Ignored 1 unit with compilation errors in first pass.
[INFO] Compile with -strict or with -logLevel set to TRACE or DEBUG to see all errors.
[INFO]    [ERROR] Module has no entry points defined
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4.786 s
[INFO] Finished at: 2015-12-22T13:36:59-08:00
[INFO] Final Memory: 11M/311M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal net.ltgt.gwt.maven:gwt-maven-plugin:1.0-SNAPSHOT:compile (default-cli) on project gwt-basic: GWT Compiler exited with status 1 -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Brandons-MacBook-Pro:gwt-basic branflake2267$ 

[branflake2267]

Oh, I found the issue. For some reason the generated module is replacing what I have. After inspecting the classes/org/gonevertical/project/Project.gwt.xml I found the generated module. Instead of generating the module, it should be copying my module. But maybe I can correct this by resource definition in the pom.xml

<module rename-to="project">
  <inherits name="com.google.gwt.core.Core"/>
  <source path="client"/>
  <source path="shared"/>
  <super-source path="super"/>
</module>

[branflake2267]

Copying the module to src/main won't work for me either.

[tbroyer]

See http://tbroyer.github.io/gwt-maven-plugin/codeserver.html for the scope issue, and http://tbroyer.github.io/gwt-maven-plugin/migrating.html about the module file.

[branflake2267]

I'm looking at the code, and it looks like the module configuration is defined in a meta-inf file, but I can't find an example yet.

[branflake2267]

From what it appears there isn't a good path to read my Project.gwt.xml file. I can see the generation mechanism, but that plants itself in the classes. I get the impression that auto generation should be doing the heavy lifting, but how would I control the permutation properties or languages?

[branflake2267]

How do you tell it to collapse a property?

[tbroyer]

"Module generation" is only about <inherits>, iff you have dependencies with META-INF/GWT/mainModule (most likely only those you built yourself as gwt-lib).
Everything else you have to put in your src/main/module.gwt.xml like in any other GWT module file.

[branflake2267]

I'm assuming I can name my gwt module descriptor something other than "module". I couldn't get that to work on my last try and gave up. Thanks for the info.

[branflake2267]

Ugh. I neglected to try to rename the module to module.gwt.xml. Seems I'm having a hard time divorcing the previously learned module descriptor custom naming.

[ibaca]

This plugin is perfect, the idea of one module autogenerated is probably a very good idea... theoretically, simplifies and unify one maven module - one gwt compilation output, but I think that in practice a lot of people coming from mojo plugin will suffer this disadvantages (at least I suffer 😜):

• at first you are not sure what's happening because you expect similar behaviour to previous plugin (means, you configure your module in the pom and you frequently expect the skipModule behaviour but you do not set skipModule).
• if you use generate module; intellij do not detect gwt correctly, because intellij uses gwt.xml in your source dir as detection point, and if gwt facet is enabled, intellij do not handle correctly module usage inspection if your gwt.xml are not in the source path (detect if you are using a class not inherited by your module); this is not a plugin problem, but this motivates not to use generate module feature
• maybe not a good practice, but sometimes more than one module/gwt app exists in the same maven module. This plugin support multi module to be manually specified in the devmode/codeserver goals but do not support to add multiple module names in the pom.

So my suggestion is...

• support multiple modules (I'll make a pull request if you think this is not a bad idea, although look like you have some motivation to not support multi-module that I'm not seeing)
• if the module name exists in the classpath, generate module must not fail and not generate anything

Maybe those problems are only for my projects... anyway, hope this helps and thanks for creating this plugin.

[branflake2267]

@ibaca Thanks for the info. I've got my module questions here and mention it b/c yours seem related #43