[
http://jira.codehaus.org/browse/MEAR-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250441#action_250441
]
Frank Griffin commented on MEAR-118:
------------------------------------
I'm still seeing this in 2.4.2:
[core.xml]
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application PUBLIC
"-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"
"http://java.sun.com/dtd/application_1_3.dtd";>
<application>
<display-name>dvd-ear</display-name>
<description>The Professional Software Services "dvd-ear" project
creates the EARFile for the "dvd" project</description>
<module>
<ejb>dvd-ejb-1.0-SNAPSHOT.jar</ejb>
</module>
</application>
> 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
> 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 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
