You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jeroen Ruijgers (JIRA)" <ji...@codehaus.org> on 2010/09/10 11:37:32 UTC
[jira] Commented: (MEAR-126) Add includeInApplicationXml property
in ejbModule
[ http://jira.codehaus.org/browse/MEAR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=234873#action_234873 ]
Jeroen Ruijgers commented on MEAR-126:
--------------------------------------
If you use an EJB as a client, you better use the ejb-client type and let maven generate the client.
An other easy solution is to add de EJB client as a JAR dependency, with has the correct behaviour.
> Add includeInApplicationXml property in ejbModule
> -------------------------------------------------
>
> Key: MEAR-126
> URL: http://jira.codehaus.org/browse/MEAR-126
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
> Reporter: Anthony Donnefort
> Priority: Minor
> Attachments: includeInApplicationXml.patch
>
>
> The ear plugin currently add all dependencies of type 'ejb' in the generated application.xml.
> Adding the property includeInApplicationXml (already present in jarModule) to the ejbModule would allow to include the jar but not deploy it, for example when it is used as a client.
> In case of the ejbModule, the default value is set to true.
> The implementation is pretty straightforward and included in this patch.
--
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