[
http://jira.codehaus.org/browse/MEAR-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129518#action_129518
]
B. Garvelink commented on MEAR-35:
----------------------------------
bq. Module ID support has been added to the EJB, JAR, and Web module types only
Thanks for the patch, the configuration parameter is the way to go. I'd like to
suggest supporting it on all module types, not just those three. The {{id}}
attribute is a special case in XML, it's allowed on any element so long as its
value is unique in the document. I see no reason to support it on an arbitrary
subset of module types. It might come in handy on one of the others.
> 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
