From: Adi B. <ad...@ti...> - 2006-02-05 10:50:14
|
Great info... (really helps) Thanks On Sun, 2006-02-05 at 11:04 +0200, Ronen Naor wrote: > If you have several web projects in Maven 2, and all of them use a g > group of identical JSP pages, you can use the derived war concept to > solve the problem. > > The idea is very simple, instead of writing in your POM, a dependency > to a JAR, like you usually write, you write a dependency to your > shared common WAR. > > For example: > > <dependency> > > <groupId>my-company</groupId> > > <artifactId>common-web</artifactId> > > <version>1.0-SNAPSHOT</version> > > <type>war</type> > > </dependency> > > The common war will be overlaid on the target project war. > > In case you need to exclude files from the common war, you can add > exclusion instruction to your POM, for example: > > <plugins> > > <plugin> > > > <artifactId>tikal-maven-war-plugin</artifactId> > > > <groupId>com.tikal.maven.plugins</groupId> > > <configuration> > > > <dependentWarExcludes>**/*</dependentWarExcludes> > > > </configuration> > > </plugin> > > </plugins> > > > > |