Saturday, April 22, 2017

Re: GWT/Maven development cycle takes much too long

On Saturday, April 22, 2017 at 5:06:00 PM UTC+2, Magnus wrote:
There may be some misunderstandings:

The question scope=provided or not affects the dependency for my own library "my-lib" in the pom.xml of my application "my-app".
    • If I remove it, the "Failed to copy file for artifact" returns (= problem 1).
    • If I keep it, the external libraries referenced by "my-lib" (like postgresql-40.0.0.jar) don't get copied into the WEB-INF/lib folder of "my-app" (problem 2).
So by changing scope=provided I can only choose between problem 1 and problem 2.

Yep, between one correct build that doesn't import in Eclipse (because of Eclipse), or an "incorrect" build (from your requirements).
Now you said that problem 2 isn't a problem, because the external libraries are provided at runtime, e. g. by Tomcat.

I'm saying you should not use scope=provided if that's not what you want (and it's not what you want, so don't use it), and find a solution (or workaround at least) for the Eclipse issue, which is BTW unrelated to GWT I believe.
You should IMO focus on the Maven part and get it right; then make it work in/with your IDE (and fully understand –and document– the changes you'll possibly need to make to make it work).

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