[
http://jira.codehaus.org/browse/MEAR-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100011
]
Jeroen Leenarts commented on MEAR-35:
-------------------------------------
I've ran into this problem as well.
Here is the use-case I am dealing with.
The module ID's are used by IBM application server 5.1 (and 6.1 for that
matter) to wire up all security roles and EJBs. While I won't be doing any
security administration myself. I do have to provide unique id's to modules.
> 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.4
>
> Attachments: 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
