Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
2.7
-
None
-
None
-
Ubuntu 9.04
Description
In my main pom.xml, I have this dependency in dependencyManagement :
<dependency>
<groupId>org.jboss.seam</groupId>
<artifactId>jboss-seam</artifactId>
<version>2.1.1.GA</version>
<type>jar</type>
</dependency>
I want to create a WAR project (and only a WAR project, not an EJB one) containing the SEAM jar. This jar has <type>ejb</type> in its pom.xml.
In my war pom.xml, I have a simple dependency to seam.jar :
<dependency>
<groupId>org.jboss.seam</groupId>
<artifactId>jboss-seam</artifactId>
</dependency>
The problem is that my generated org.eclipse.wst.common.component contains two <dependent-module archiveName="jboss-seam-2.1.1.GA.jar"/> with 2 different deploy-path. ("/" and "/WEB-INF/lib"). As I only want to create a war, I want that jar to be deployed in /WEB-INF/lib. That configuration makes Eclipse to create a WAR with jboss-seam-2.1.1.GA.jar in the root of my war, and not in the WEB-INF/lib folder (so my application server don't load SEAM).
I'm using wtpversion 2.0 (but I've tested with 1.5, it's the same result), maven-war-plugin 2.0.2 and maven-eclipse-plugin 2.7.