Hi all, Option 1: It's easy to write a POM that creates a JAR for a GWT widget including CSS and other resources. It's also easy to then write a POM that depends on that JAR and creates a WAR for integration testing. So far so good. Problem: Making changes in (e.g.) the CSS requires a full rebuild of both the JAR and the WAR. This is a real productivity issue.
Option 2: Put everything in a single WAR project. Integration testing uses this WAR and development can make changes that are reflected after a simple refresh. Problem: We need a JAR, not a WAR for our other GWT projects that want to reuse the widget. The only "solution" that I can see is to go with option 2 and create a second (JAR) project that depends on the WAR and strips away all its "web-app-ness" to create the JAR I referred to in option 1. This achieves all my goals but isn't very elegant. Can anyone think of a better way to do this? Cheers, Hilco --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
