Yes, it's common to have the code in a separate module from the webapp. It makes it easier to do unit testing of the code separately from integration testing the webapp.
I'm not sure how that relates to your original question though. I see the jar module and the war module... where is the assembly plugin configured? (Or, were you using 'assembly' in a generic sense?) If you're just trying to convince Maven not to put your JDBC driver in the war, try using 'provided' scope for that dependency. -- Wendy On Fri, Aug 28, 2009 at 1:31 PM, James Russo<j...@halo3.net> wrote: > Hello, > > So, the recommended way is to have something like this, correct? > > xx-weblogic (all code for web-application) > xx-webapp (the actual war, containing src/main/webapp, src/main/resources, > but no src/main. Code is really included though .jar files in lib). ... --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
