You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Armin Wrobel (JIRA)" <ji...@codehaus.org> on 2010/01/21 17:41:55 UTC
[jira] Created: (MEAR-122) Setting of in pom.xml is
ignored. ArtifactId of a WebModule is set as context-root in the
application.xml instead.
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
Affects Versions: 2.4
Environment: Maven 2.0.10
Windows XP SP3
Reporter: Armin Wrobel
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
[jira] Closed: (MEAR-122) Setting of in pom.xml is
ignored. ArtifactId of a WebModule is set as context-root in the
application.xml instead.
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephane Nicoll closed MEAR-122.
--------------------------------
Resolution: Not A Bug
Fix Version/s: 2.4.1
Assignee: Stephane Nicoll
You can't do that! You are overriding the modules section in both profile and since common-profile is first, it takes precendence. There is no merging of attributes in a plugin. Consider the list of modules the same as the description or display name for instance. If you set this value in both profile, you're not expecting a combination of the two values right?
You should pay attention with the way you use profile, I don't think it is very safe and leads to reproductible build. Maybe you need the rethink the way you design your build.
That being said, removing the empty modules in the default profile (?!) does what you expect.
> 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
[jira] Commented: (MEAR-122) Setting of in pom.xml is
ignored. ArtifactId of a WebModule is set as context-root in the
application.xml instead.
Posted by "Armin Wrobel (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207887#action_207887 ]
Armin Wrobel commented on MEAR-122:
-----------------------------------
Stephane, thanks for looking at this issue! Your help is highly appreciated!
I'm using version 2.4 of the maven-ear-plugin.
True, I complained only about the incorrect context of one of the web modules. Unfortunately, the context is set wrongly for all of them. I remember working with this property in earlier (single module) projects, and there it worked correctly. Somehow in a multi module project there can be a certain situation where the contextRoot doesn't work anymore.
Do you have any fix or workaround for this?
> 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
> Affects Versions: 2.4
> Environment: Maven 2.0.10
> Windows XP SP3
> Reporter: Armin Wrobel
> Attachments: 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
[jira] Updated: (MEAR-122) Setting of in pom.xml is
ignored. ArtifactId of a WebModule is set as context-root in the
application.xml instead.
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephane Nicoll updated MEAR-122:
---------------------------------
Affects Version/s: (was: 2.4)
> 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
[jira] Commented: (MEAR-122) Setting of in pom.xml is
ignored. ArtifactId of a WebModule is set as context-root in the
application.xml instead.
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207886#action_207886 ]
Stephane Nicoll commented on MEAR-122:
--------------------------------------
This is not a sample project. I won't be able to execute it over here
> 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
> Affects Versions: 2.4
> Environment: Maven 2.0.10
> Windows XP SP3
> Reporter: Armin Wrobel
> Attachments: 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
[jira] Updated: (MEAR-122) Setting of in pom.xml is
ignored. ArtifactId of a WebModule is set as context-root in the
application.xml instead.
Posted by "Armin Wrobel (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Armin Wrobel updated MEAR-122:
------------------------------
Attachment: pom.xml
Parent POM
> 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
> Affects Versions: 2.4
> Environment: Maven 2.0.10
> Windows XP SP3
> Reporter: Armin Wrobel
> Attachments: 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
[jira] Commented: (MEAR-122) Setting of in pom.xml is
ignored. ArtifactId of a WebModule is set as context-root in the
application.xml instead.
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207890#action_207890 ]
Stephane Nicoll commented on MEAR-122:
--------------------------------------
can you do {{mvn clean package -X > output.log}} on the project and attach the log please?
> 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
> Affects Versions: 2.4
> Environment: Maven 2.0.10
> Windows XP SP3
> Reporter: Armin Wrobel
> Attachments: 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
[jira] Commented: (MEAR-122) Setting of in pom.xml is
ignored. ArtifactId of a WebModule is set as context-root in the
application.xml instead.
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207832#action_207832 ]
Stephane Nicoll commented on MEAR-122:
--------------------------------------
well, you have two of them in your pom and you don't seem to complain about it, right? There are tests that validate this scenario. Can you post a sample project that reproduces the issue? What version of the ear plugin are you using?
> 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
> Affects Versions: 2.4
> Environment: Maven 2.0.10
> Windows XP SP3
> Reporter: Armin Wrobel
>
> 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
[jira] Commented: (MEAR-122) Setting of in pom.xml is
ignored. ArtifactId of a WebModule is set as context-root in the
application.xml instead.
Posted by "Tiago Torres (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MEAR-122) Setting of in pom.xml is
ignored. ArtifactId of a WebModule is set as context-root in the
application.xml instead.
Posted by "Armin Wrobel (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Armin Wrobel updated MEAR-122:
------------------------------
Attachment: pom.xml
POM of EAR module where I try to set the contextRoot of several web modules.
> 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
> Affects Versions: 2.4
> Environment: Maven 2.0.10
> Windows XP SP3
> Reporter: Armin Wrobel
> Attachments: 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
[jira] Updated: (MEAR-122) Setting of in pom.xml is
ignored. ArtifactId of a WebModule is set as context-root in the
application.xml instead.
Posted by "Armin Wrobel (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Armin Wrobel updated MEAR-122:
------------------------------
Attachment: ecase.zip
output.log
The requested debug info trace file and the sample project.
I created a sample project for you, and this output.log has been created using the sample project.
In the sample project I removed everything, but two modules besides the ear module. One is a webservice module and the other the ecase-web module.
As soon as I comment the dependency and module definition of 'ecase-sunet-ws' in the ear pom out, the contextRoot of the 'ecase-web' artifact is set correctly in the application.xml as '/ecase'. Otherwise it's set as '/ecase-web' which is the artifactId.
As I can see in the debug info, only the ecase-sunet-ws contextRoot setting is considered in the case where both modules are configured.
The maven build has to be started like this: mvn clean package -Pcommon-profile,casex-ext
Again, thanks a lot for your help! You're doing a great job!
Armin
> 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
> Affects Versions: 2.4
> Environment: Maven 2.0.10
> Windows XP SP3
> Reporter: Armin Wrobel
> 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