> given (client and webapp are two distinct maven project with their own > pom.xml), > which of the solutions below is the correct way for resolving dependency, > given the assumptions in previous posts (multi-module gwt project) > 1- copy assembled zip file from client project directory, to webapp project > directory > 2- install assembled zip file from client project into local repository, so > that webapp project can then grab it from local repository ?
2, if you care about the modularity that your maven project structure defines. You shouldn't reach across those boundaries just because you know the other module happens to be at a particular path relative to the WAR module. Use the assembly plugin as someone suggested in another thread. Or, you can use dependency management. In the project I'm working on, I put the GWT code in a separate WAR module. I then added a dependency to that module from our main WAR module. This causes a WAR overlay to be done during the build of the main WAR. The downside is that you have to maintain any GWT-related servlet mappings and such in web.xml of both projects. The upside is that I can run GWT features without building the entire main WAR. -Brian -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
