You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stephen Coy (JIRA)" <ji...@codehaus.org> on 2009/12/02 07:47:55 UTC
[jira] Created: (MEAR-118) Invalid application.xml generated
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
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
[jira] Closed: (MEAR-118) Invalid application.xml generated
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephane Nicoll closed MEAR-118.
--------------------------------
Resolution: Fixed
Fixed. Deployed a new 2.4.1 snapshot
> 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
[jira] Commented: (MEAR-118) Invalid application.xml generated
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207147#action_207147 ]
Stephane Nicoll commented on MEAR-118:
--------------------------------------
Stephen, I know about that trust me :) I found out that myself while implementing the feature. Unfortunately, a regression was introduced recently. I will fix the code and add more comments so that people are more careful with this.
> 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
[jira] Commented: (MEAR-118) Invalid application.xml generated
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MEAR-118) Invalid application.xml generated
Posted by "Markku Saarela (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204265#action_204265 ]
Markku Saarela commented on MEAR-118:
-------------------------------------
This bug blocks my usage of this version of plugin, because WebSphere 7 uses Eclipse WST tooling for parsing application.xml and deployment to WAS fails due to wrong order of elements. Version 2.3 has correct sequence of elements.
> 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
>
> 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
[jira] Work started: (MEAR-118) Invalid application.xml generated
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on MEAR-118 started by Stephane Nicoll.
> 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
[jira] Issue Comment Edited: (MEAR-118) Invalid application.xml
generated
Posted by "Stephen Coy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250451#action_250451 ]
Stephen Coy edited comment on MEAR-118 at 1/4/11 4:17 PM:
----------------------------------------------------------
This is correct for J2EE 1.3.
J2EE 1.4 moved from DTDs to schemas where the order of the elements was made more consistent for all of the different deployment descriptors.
Perhaps you need to specify the J(2)EE version in the plugin config?
was (Author: sfcoy):
This is correct for J2EE 1.3.
J2EE 1.4 moved from DTDs to schemas where the order of the elements was made more consistent for all of the different deployment descriptors.
> 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
[jira] Commented: (MEAR-118) Invalid application.xml generated
Posted by "Stephen Coy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207026#action_207026 ]
Stephen Coy commented on MEAR-118:
----------------------------------
Be very careful with this because the order of the elements was reversed between J2EE 1.3 and J2EE 1.4.
This plugin currently works correctly for J2EE 1.3 ear files.
> 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
[jira] Updated: (MEAR-118) Invalid application.xml generated
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephane Nicoll updated MEAR-118:
---------------------------------
Fix Version/s: 2.4.1
> 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
>
>
> 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
[jira] Commented: (MEAR-118) Invalid application.xml generated
Posted by "Stephen Coy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250451#action_250451 ]
Stephen Coy commented on MEAR-118:
----------------------------------
This is correct for J2EE 1.3.
J2EE 1.4 moved from DTDs to schemas where the order of the elements was made more consistent for all of the different deployment descriptors.
> 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
[jira] Commented: (MEAR-118) Invalid application.xml generated
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210340#action_210340 ]
Stephane Nicoll commented on MEAR-118:
--------------------------------------
we will of course release it.
> 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
[jira] Commented: (MEAR-118) Invalid application.xml generated
Posted by "Vincent Latombe (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207029#action_207029 ]
Vincent Latombe commented on MEAR-118:
--------------------------------------
Please check the patch I attached, for me it fixes the problem.
> 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
[jira] Commented: (MEAR-118) Invalid application.xml generated
Posted by "Frank Griffin (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MEAR-118) Invalid application.xml generated
Posted by "Vincent Latombe (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent Latombe updated MEAR-118:
---------------------------------
Attachment: ApplicationXmlWriter.java.patch
Regression occured when introducing JEE6 support
> 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
[jira] Commented: (MEAR-118) Invalid application.xml generated
Posted by "fabrice (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210333#action_210333 ]
fabrice commented on MEAR-118:
------------------------------
hi
Why do you not create a release instead of snapshot ?
> 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
[jira] Commented: (MEAR-118) Invalid application.xml generated
Posted by "Paul Merlin (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=202721#action_202721 ]
Paul Merlin commented on MEAR-118:
----------------------------------
I confirm this issue with maven 2.2.1 and maven-ear-plugin 2.4.
> 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
>
> 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