Saturday, April 22, 2017

Re: GWT/Maven development cycle takes much too long

Hello Jens,

I'm beginning to realize that removing scope=provided isn't a solution to the eclipse problem.
Sorry that this took so long...

However, then let's come back to the eclipse error again:

org.apache.maven.plugin.MojoExecutionException: Failed to copy file for artifact [msm.lib.acs:msm-lib-acs:jar:1.0-SNAPSHOT:compile]
Caused by: /home/wagner/dvl/prj/msm/msm-lib-acs/target/classes (Is a directory)

I see two approaches then:

  • solve the eclipse error without removing scope=provided
    Does anyone have an idea what may be causing the eclipse error? What file is not found? What is the process behind this file access? Can you solve it by placing a dummy file somewhere?

  • using another maven plugin
    As some of you may have noticed in another thread, I was evaluating both, Mojo's and Thomas' eclipse plugin. Then, I saw that I can live with the pom.xml created by webAppCreator, without really caring about which plugin is used then.
    But I thought it was the "GWT way to go", since the pom was created by webAppCreator, which is shipped with the GWT SDK.

    However, in this thread, Thomas said that the Mojo-Haus plugin doesn't work in reactor builds. But I was unsure what I am actually using. When looking into my pom.xml I see a plugin with groupId = net.ltgt.gwt.maven. This seems to refer to Thomas' plugin. But in contrast, the error message refers to "MojoExecutionException". Sorry, but I still cannot follow this. Which plugin am I using? And if it's the "wrong" one, how can I switch in my existing pom.xml?
There seem to exist people without those problems. I simply want to do it the same way.


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
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment