On Thu, Nov 6, 2008 at 7:09 PM, Milo Mo <[EMAIL PROTECTED]> wrote: > I can't help thinking that declaring "jar" packaging in App1 and App2 is a > bit of a hack. Is there a better way of doing this? Web apps depending on > java classes in other web apps must be a standard issue when building multi > projects. Another solution is breaking out the classes from App1 and App2 > that Admin needs, but that means two more projects (e.g. "App1-common" and > "App2-common"), and I think 6 maven projects for two web applications + > admin is a bit much. >
You could put all the classes for App1 and App2 in a single module -- so now you have one jar and three war modules. Or all the common classes in one module - one jar and three wars again. The simplest thing to do what you're already doing probably is to use the WAR overlay technique: http://maven.apache.org/plugins/maven-war-plugin/overlays.html - Geoffrey -- Geoffrey Wiseman
