[
http://jira.codehaus.org/browse/MEAR-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207025#action_207025
]
Stephane Nicoll commented on MEAR-118:
--------------------------------------
Yup, I suspected that too. I have created a 2.4.1 release to quickly fix that
one.
> Invalid application.xml generated
> ---------------------------------
>
> Key: MEAR-118
> URL: http://jira.codehaus.org/browse/MEAR-118
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.4
> Environment: Maven 2.2.1
> Reporter: Stephen Coy
> Priority: Critical
> Fix For: 2.4.1
>
> Attachments: ApplicationXmlWriter.java.patch
>
>
> If a project description is specified in the pom.xml, then the plugin
> generates a corresponding <description>description from pom</description>
> element in the application.xml file.
> Unfortunately, it places it in the wrong location according to the schema
> (for both J2EE 1.4 and JEE 5):
> <display-name>artifact name</display-name>
> <description>project description</description>
> <module>
> ...
> instead of:
> <description>project description</description>
> <display-name>artifact name</display-name>
> <module>
> ...
> This results in deployment failure on WebSphere.
> Work around is to roll back to version 2.3.2 of the ear plugin.
--
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
