Friday, April 21, 2017

Re: GWT/Maven development cycle takes much too long

Hi Thomas,

I already have started to play with a reactor. Below is my top-level pom.xml. But where to go from here?
What are the mvn commands to build everything on the top-level? If "mvn install" isn't needed anymore, how does the app project see the library?

This is also the point with the development cycle: When debugging, eclipse doesn't "see" the changed library source code, because it fetches the library source code from the jar file in its own target folder. And this jar file is updated only by "mvn install" at the app project. Wouldn't it be better for developing if the original library code was used instead? Could it be that this is the core of the problem?


<project xmlns="" xmlns:xsi=""






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