On Feb 19, 2008 9:56 PM, Chris <[EMAIL PROTECTED]> wrote:
> We have two webapps. One is the basic app, and one is the enhanced
> version of the same app.
>
> In our current setup, when we want to run the enhanced app we copy the
> basic app into /webapps/mywebapp, then we overwrite the directory with
> the files from the enhanced app. This is necessary because the enhanced
> app replaces index.jsp, some of the .css files, and a number of other pages.
>
> This scheme works fine, but now I'm migrating to Maven, and this isn't a
> very maven-ish way to do things. Is there a more standard way to handle
> the situation when one webapp depends on another?
If I'm reading correctly:
* create war project (packaging==war), the basic one;
* handle basic app in standard maven way (install/deploy/release and so on);
* create war project (...), enhanced one, adding
<dependency>
<groupId>yourgroupid</groupId>
<artifactId>basic one</artifactId>
<version>I-do-not-know-but-you-know-for-sure</version>
<type>war</type>
</dependency>
and during 'package' maven will unpack 'basic' one and copy resources
(src/main/webapp and so on) from enhanced (so you may override 'basic'
things like web.xml).
Which is probably exactly what you're looking for and is in maven way.
More about this here:
http://maven.apache.org/plugins/maven-war-plugin/overlays.html
HTH,
Tomek
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
