I'm a little new to Maven (about 3 weeks), so I apologize if this is a n00b question. I have a question about how to better structure my current application. Currently, the parent project has three modules: client, server, and common. Common depends on nothing. It simply hold beans and service interfaces that are common across the app. Server depends on Common. Client depends on Server. Common and Server are packaged as JARs. Client is packaged as a WAR. When I want to deploy my application, I simply build the client and all is well. This means I have to put all my Spring related configurations in the client. I was hoping there was a way to avoid this by putting it in the Server module, but I don't see how that's possible if the Server module is packaged as a JAR. Am I going about this the wrong way?
-- Matthew Walsh [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
