[
https://issues.apache.org/jira/browse/MEAR-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17959010#comment-17959010
]
Matthias Bünger commented on MEAR-118:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-ear-plugin#309|https://github.com/apache/maven-ear-plugin/issues/309].
> Invalid application.xml generated
> ---------------------------------
>
> Key: MEAR-118
> URL: https://issues.apache.org/jira/browse/MEAR-118
> Project: Maven EAR Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 2.4
> Environment: Maven 2.2.1
> Reporter: Stephen Coy
> Assignee: Stephane Nicoll
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
