[
http://jira.codehaus.org/browse/MEAR-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=133100#action_133100
]
Julien HENRY commented on MEAR-35:
----------------------------------
I'm new to EAR and WebSphere but it seems I will need an ID on the application
tag also. Here is an existing application.xml used by the old Ant build:
{code:xml}
<?xml version="1.0" encoding="ISO-8859-15"?>
<!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application
1.3//EN" "http://java.sun.com/dtd/application_1_3.dtd";>
<application id="Application_ID">
<display-name>MyApp</display-name>
<module id="WebModule_1102675755495">
<web>
<web-uri>app.war</web-uri>
<context-root>/app</context-root>
</web>
</module>
<security-role id="SecurityRole_1102689931785">
<description></description>
<role-name>appuser</role-name>
</security-role>
</application>
{code}
> Generate id for modules in application.xml
> ------------------------------------------
>
> Key: MEAR-35
> URL: http://jira.codehaus.org/browse/MEAR-35
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
> Reporter: Manikandan Balasubramanian
> Priority: Minor
> Fix For: 2.3.2
>
> Attachments: ear-module-id.patch, MEAR-35-maven-ear-plugin-2.patch,
> MEAR-35-maven-ear-plugin.patch
>
>
> When the ear plugin generates application.xml, it should generate an "id"
> with each module. This "id" is according to application.xml schema.
> This would help eclipse plugin to generate correct eclipse metedata.
--
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
