No source code is available for type about gwt-maven-plugin HOT 4 CLOSED

Hi.

The project complains about missing dependencies:

[ERROR] Failed to execute goal on project hal-processors: Could not resolve dependencies for project org.jboss.hal:hal-processors:jar:0.0.2: Failure to find org.jgrapht:jgrapht-core:jar:0.9.2-hal 

But I think the real problem is that you are not using src/main/module.gwt.xml. For instance, your org/jboss/hal/Ballroom.gwt.xml is being ignored. The ballroom/target/classes/org/jboss/hal/Ballroom.gwt.xml is automatically generated by the plugin and includes the src/main/module.gwt.xml.

If you really want to use org/jboss/hal/Ballroom.gwt.xml instead of src/main/module.gwt.xml you have to add to the plugin configuration.

from gwt-maven-plugin.

Thanks @natros, works like a charme! I didn't know that I should use module.gwt.xml files to declare my GWT modules. They're quite handy, though. BTW my maven project uses APT to generate code which is picked up by the GWT compiler.

@tbroyer Maybe it's worth to add some documentation in [1]. Coming from the Codehaus GWT maven module I wanted to reuse my existing GWT modules. However it's much more simpler to switch over to module.gwt.xml files.

[1] https://tbroyer.github.io/gwt-maven-plugin/migrating.html

from gwt-maven-plugin.

Yes, it really needs to be better documented (and not only in the migrating page). I'll leave this issue open for now as a reminder (aka repurposing as a documentation issue).

Thank you both for the feedback and early adoption.

from gwt-maven-plugin.

In retrospect, I think I expected resources:resources to overwrite the module file generated by gwt:generate-module. Maybe it work with some version of the maven-resources-plugin (default one depending on the Maven version) and not with others. Anyway, this is now documented eb80130

from gwt-maven-plugin.