[
http://jira.codehaus.org/browse/MEAR-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeroen Leenarts updated MEAR-35:
--------------------------------
Attachment: MEAR-35-maven-ear-plugin-2.patch
The current work-around I am using right now. (we're running an inhouse
repository by overriding central)
It's a bit different compared to the earlier patch. With this patch I can use a
"moduleId" element within my ejbModule items. I've done this for the ejbModule
only because this is just a proof of concept.
> 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-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
