[
http://jira.codehaus.org/browse/MEAR-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=228745#action_228745
]
Tiago Torres commented on MEAR-122:
-----------------------------------
Stephane, I have a question. If I understood correctly, I can't declare a
maven-ear-plugin section inside a custom profile if I already have this section
in the default profile. Does that mean I can never have a web module dependency
in a custom profile in case I already have a maven-ear-plugin declared in my
default profile? Is there a workaround for this problem?
Thanks,
Tiago
> Setting of <contextRoot> in pom.xml is ignored. ArtifactId of a WebModule is
> set as context-root in the application.xml instead.
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: MEAR-122
> URL: http://jira.codehaus.org/browse/MEAR-122
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Environment: Maven 2.0.10
> Windows XP SP3
> Reporter: Armin Wrobel
> Assignee: Stephane Nicoll
> Fix For: 2.4.1
>
> Attachments: ecase.zip, output.log, pom.xml, pom.xml
>
>
> I set in my POM the desired context root of a web module which is to be
> bundled in a EAR file.
> The <contextRoot> setting is simply ignored when building the EAR file.
> Instead the artifactId of the web module is used.
> This is the webModule with the ignored contextRoot:
> <webModule>
> <groupId>ch.hrms.ecase</groupId>
> <artifactId>ecase-web</artifactId>
> <contextRoot>/ecase</contextRoot>
> </webModule>
> Following is a larger snippet of the POM:
> <profile>
> <id>casex-ext</id>
> <dependencies>
> <dependency>
> <groupId>ch.hrms.ecase</groupId>
> <artifactId>ecase-ws</artifactId>
> <version>${applicationVersion}</version>
> <type>wsr</type>
> </dependency>
> <dependency>
> <groupId>ch.hrms.ecase</groupId>
> <artifactId>ecase-sunet-ws</artifactId>
> <version>${applicationVersion}</version>
> <type>war</type>
> </dependency>
> <dependency>
> <groupId>ch.hrms.ecase</groupId>
> <artifactId>ecase-pdf</artifactId>
> <version>${applicationVersion}</version>
> <type>sar</type>
> </dependency>
> <dependency>
> <groupId>ch.hrms.ecase</groupId>
> <artifactId>ecase-web</artifactId>
> <version>${applicationVersion}</version>
> <type>war</type>
> </dependency>
> <dependency>
> <groupId>ch.hrms.ecase</groupId>
> <artifactId>rootCtx</artifactId>
> <version>${applicationVersion}</version>
> <type>war</type>
> </dependency>
> </dependencies>
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-ear-plugin</artifactId>
> <configuration>
> <displayName>eCaseSwica - external</displayName>
> <finalName>ecase-swica-ext</finalName>
> <description>
> eCase for Swica - deployment for external JBoss server
> </description>
> <modules>
> <wsrModule>
> <groupId>ch.hrms.ecase</groupId>
> <artifactId>ecase-ws</artifactId>
> </wsrModule>
> <webModule>
> <groupId>ch.hrms.ecase</groupId>
> <artifactId>ecase-sunet-ws</artifactId>
> <contextRoot>/sunet/ws/casedata</contextRoot>
> </webModule>
> <sarModule>
> <groupId>ch.hrms.ecase</groupId>
> <artifactId>ecase-pdf</artifactId>
> </sarModule>
> <webModule>
> <groupId>ch.hrms.ecase</groupId>
> <artifactId>ecase-web</artifactId>
> <contextRoot>/ecase</contextRoot>
> </webModule>
> <webModule>
> <groupId>ch.hrms.ecase</groupId>
> <artifactId>rootCtx</artifactId>
> </webModule>
> </modules>
> </configuration>
> </plugin>
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>jboss-maven-plugin</artifactId>
> <version>1.4</version>
> <configuration>
> <port>8180</port>
> <jbossHome>${JBoss_Ext_Home}</jbossHome>
> <fileName>ecase-ear/target/ecase-swica-ext.ear</fileName>
> </configuration>
> </plugin>
> </plugins>
> </build>
> </profile>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
