Saturday, April 22, 2017

Re: GWT/Maven development cycle takes much too long

 
And unfortunately this problem now reappeared. When I build the app with "mvn package", I end ab with a WEB-INF/lib folder not containing the external libs!
 
This is expected: scope=provided means "this will be provided by 'the environment'" so it's not packaged inside the WAR (and transitive dependencies as well, of course).
And because the error you're having specifically happens when trying to copy the JAR into the WEB-INF/lib, if you say that this should no longer happen (by using scope=provided), then the error goes away.
 
Maybe another scope is better?

No.
The problem is that Eclipse wants to package your app.

This problem is outside eclipse. When I "mvn package" the app it results in missing libs in the WEB-INF/lib folder.
How can I solve that?

Magnus

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment