On Tuesday, July 17, 2012 4:53:12 PM UTC+2, dhoffer wrote: > > I'm assuming that classes in GWT's client folder have no reason to be > compiled into classes and go into the war's WEB-INF/classes folder as GWT > already converted that to JavaScript but what's the best way to prevent > this? I'm using the gwt-maven-plugin to compile the GWT code in my war > maven module.
IMO, the best way is to use separate projects for client and server code (see https://github.com/tbroyer/gwt-maven-archetypes for examples) Alternately, you can use maven-war-plugin's packagingExclude to exclude WEB-INF/classes/**/client/** classes (and make sure you set all your GWT dependencies –GIN, GXT, whatever– as scope=provided so they don't go in WEB-INF/lib either). (actually, my archetypes use this in the 'client' module to exclude everything from WEB-INF/ and thus only keep the generated scripts and resources in the client WAR, which is then used as an overlay in the 'server' module that contains the web.xml, index.html, and servlets and other server-side code and dependencies) -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/fRPALn54S_EJ. 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.
