[
https://jira.codehaus.org/browse/MWAR-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MWAR-222:
---------------------------------
Component/s: overlay
Description:
I have a webCommon project sharing its content with webA, webB project via
overlay mechanism.
The resulting war in webA and webB project have webCommon webapps (web is my
warSourceDirectory) content in the root and in WEB-INF/classes too!
Why? Is this the right behavior? How to avoid it?
webCommon pom.xml is like that:
{code:xml}
<packaging>war</packaging>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>2.1-beta-1</version>
<configuration>
<warName>esse3</warName>
<warSourceDirectory>web</warSourceDirectory>
<failOnMissingWebXml>false</failOnMissingWebXml>
</configuration>
</plugin>
</plugins>
</build>
{code}
webX pom is like this:
{code:xml}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>2.1-beta-1</version>
<configuration>
<warName>esse3</warName>
<failOnMissingWebXml>true</failOnMissingWebXml>
<warSourceDirectory>web</warSourceDirectory>
<overlays>
<overlay>
<groupId>it.kion.esse3</groupId>
<artifactId>webCommon</artifactId>
</overlay>
</overlays>
</configuration>
</plugin>
{code}
was:
I have a webCommon project sharing its content with webA, webB project via
overlay mechanism.
The resulting war in webA and webB project have webCommon webapps (web is my
warSourceDirectory) content in the root and in WEB-INF/classes too!
Why? Is this the right behavior? How to avoid it?
webCommon pom.xml is like that:
<packaging>war</packaging>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>2.1-beta-1</version>
<configuration>
<warName>esse3</warName>
<warSourceDirectory>web</warSourceDirectory>
<failOnMissingWebXml>false</failOnMissingWebXml>
</configuration>
</plugin>
</plugins>
</build>
webX pom is like this:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>2.1-beta-1</version>
<configuration>
<warName>esse3</warName>
<failOnMissingWebXml>true</failOnMissingWebXml>
<warSourceDirectory>web</warSourceDirectory>
<overlays>
<overlay>
<groupId>it.kion.esse3</groupId>
<artifactId>webCommon</artifactId>
</overlay>
</overlays>
</configuration>
</plugin>
> War overlay copy warSourceDirectory of the source in the dependent
> WEB-INF/classes
> -----------------------------------------------------------------------------------
>
> Key: MWAR-222
> URL: https://jira.codehaus.org/browse/MWAR-222
> Project: Maven 2.x WAR Plugin
> Issue Type: Bug
> Components: overlay
> Affects Versions: 2.1-beta-1
> Reporter: Matteo Turra
>
> I have a webCommon project sharing its content with webA, webB project via
> overlay mechanism.
> The resulting war in webA and webB project have webCommon webapps (web is my
> warSourceDirectory) content in the root and in WEB-INF/classes too!
> Why? Is this the right behavior? How to avoid it?
> webCommon pom.xml is like that:
> {code:xml}
> <packaging>war</packaging>
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-war-plugin</artifactId>
> <version>2.1-beta-1</version>
> <configuration>
> <warName>esse3</warName>
>
> <warSourceDirectory>web</warSourceDirectory>
>
> <failOnMissingWebXml>false</failOnMissingWebXml>
> </configuration>
> </plugin>
> </plugins>
> </build>
> {code}
> webX pom is like this:
> {code:xml}
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-war-plugin</artifactId>
> <version>2.1-beta-1</version>
> <configuration>
> <warName>esse3</warName>
> <failOnMissingWebXml>true</failOnMissingWebXml>
> <warSourceDirectory>web</warSourceDirectory>
> <overlays>
> <overlay>
> <groupId>it.kion.esse3</groupId>
> <artifactId>webCommon</artifactId>
> </overlay>
> </overlays>
> </configuration>
> </plugin>
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
