[ http://jira.codehaus.org/browse/MEAR-29?page=all ]
Stephane Nicoll updated MEAR-29:
--------------------------------
Description:
I embed a WAR portlet module inside an EAR module
I configure the EAR module as follows
<plugin>
<groupId> org.apache.maven.plugins</groupId>
<artifactId>maven-ear-plugin</artifactId>
<version>2.1</version>
<configuration>
<displayName>Portlet</displayName>
<description>JBOSS portlet</description>
<modules>
<webModule>
<groupId>myApp</groupId>
<artifactId>JBPortlet1-war</artifactId>
<!--<contextRoot>/portlet</contextRoot> <<<< My
problem goes here -->
</webModule>
</modules>
</configuration>
</plugin>
The maven-EAR-module generates an application.xml of the following form:
<application>
<display-name>Thierry Portlet</display-name>
<description>JBOSS portlet</description>
<module>
<web>
<web-uri> JBPortlet1-war-1.0.war</web-uri>
<context-root>/portlet</context-root> <<< I would like to
remove automatically this line
</web>
</module>
</application>
The problem is:
In case of a portlet deployment, the <context-root> element must be omitted, or
the application server reject the EAR package.
There is no way today to disable <context-root> generation in application.xml
If i comment / remove the <contextroot> line in the POM file , it takes the WAR
filename as context-root in the application.xml
I would like to remove automatically the <context-root> line.
what could be the strategy?
=>a <noContextRoot> tag added to the ear plugin config
<webModule>
<groupId>tutorials</groupId>
<artifactId>JBPortlet1-war</artifactId>
<noContextRoot/>
</webModule>
=>a way to specify that application-xml has to be generated regarding portlet
constraints? (<isPortlet> property)
<webModule>
<groupId>tutorials</groupId>
<artifactId>JBPortlet1-war</artifactId>
<isPortlet>true</isPortlet>
</webModule>
was:
I embed a WAR portlet module inside an EAR module
I configure the EAR module as follows
<plugin>
<groupId> org.apache.maven.plugins</groupId>
<artifactId>maven-ear-plugin</artifactId>
<version>2.1</version>
<configuration>
<displayName>Portlet</displayName>
<description>JBOSS portlet</description>
<modules>
<webModule>
<groupId>myApp</groupId>
<artifactId>JBPortlet1-war</artifactId>
<!--<contextRoot>/portlet</contextRoot> <<<< My
problem goes here -->
</webModule>
</modules>
</configuration>
</plugin>
The maven-EAR-module generates an application.xml of the following form:
<application>
<display-name>Thierry Portlet</display-name>
<description>JBOSS portlet</description>
<module>
<web>
<web-uri> JBPortlet1-war-1.0.war</web-uri>
<context-root>/portlet</context-root> <<< I would like to
remove automatically this line
</web>
</module>
</application>
The problem is:
In case of a portlet deployment, the <context-root> element must be omitted, or
the application server reject the EAR package.
There is no way today to disable <context-root> generation in application.xml
If i comment / remove the <contextroot> line in the POM file , it takes the WAR
filename as context-root in the application.xml
I would like to remove automatically the <context-root> line.
what could be the strategy?
=>a <noContextRoot> tag added to the ear plugin config
<webModule>
<groupId>tutorials</groupId>
<artifactId>JBPortlet1-war</artifactId>
<noContextRoot/>
</webModule>
=>a way to specify that application-xml has to be generated regarding portlet
constraints? (<isPortlet> property)
<webModule>
<groupId>tutorials</groupId>
<artifactId>JBPortlet1-war</artifactId>
<isPortlet>true</isPortlet>
</webModule>
Fix Version: 2.3
> EAR:generate-application-xml : Ability to deactivate <context-root>
> generation to be compliant with portlet deployment
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: MEAR-29
> URL: http://jira.codehaus.org/browse/MEAR-29
> Project: Maven 2.x Ear Plugin
> Type: Improvement
> Versions: 2.1
> Environment: OS: WIN2K (likely any platform)
> Application Server: JBOSS 4.0.3 (likely not relevant)
> Reporter: Thierry Barnier
> Assignee: Stephane Nicoll
> Fix For: 2.3
> Attachments: no-context-root for Maven-EARplugin.patch
>
>
> I embed a WAR portlet module inside an EAR module
> I configure the EAR module as follows
> <plugin>
> <groupId> org.apache.maven.plugins</groupId>
> <artifactId>maven-ear-plugin</artifactId>
> <version>2.1</version>
> <configuration>
> <displayName>Portlet</displayName>
> <description>JBOSS portlet</description>
> <modules>
> <webModule>
> <groupId>myApp</groupId>
> <artifactId>JBPortlet1-war</artifactId>
> <!--<contextRoot>/portlet</contextRoot> <<<< My
> problem goes here -->
> </webModule>
> </modules>
> </configuration>
> </plugin>
> The maven-EAR-module generates an application.xml of the following form:
> <application>
> <display-name>Thierry Portlet</display-name>
> <description>JBOSS portlet</description>
> <module>
> <web>
> <web-uri> JBPortlet1-war-1.0.war</web-uri>
> <context-root>/portlet</context-root> <<< I would like to
> remove automatically this line
> </web>
> </module>
> </application>
> The problem is:
> In case of a portlet deployment, the <context-root> element must be omitted,
> or the application server reject the EAR package.
> There is no way today to disable <context-root> generation in application.xml
> If i comment / remove the <contextroot> line in the POM file , it takes the
> WAR filename as context-root in the application.xml
> I would like to remove automatically the <context-root> line.
> what could be the strategy?
> =>a <noContextRoot> tag added to the ear plugin config
> <webModule>
> <groupId>tutorials</groupId>
> <artifactId>JBPortlet1-war</artifactId>
> <noContextRoot/>
> </webModule>
> =>a way to specify that application-xml has to be generated regarding portlet
> constraints? (<isPortlet> property)
> <webModule>
> <groupId>tutorials</groupId>
> <artifactId>JBPortlet1-war</artifactId>
> <isPortlet>true</isPortlet>
> </webModule>
--
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
