[
http://jira.codehaus.org/browse/MEAR-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132975#action_132975
]
James Olsen commented on MEAR-85:
---------------------------------
Another workaround that can help is to declare the dependency with:
<classifier>client</classifier>
instead of:
<type>ejb-client</type>
Then the ejbClientModule workaround isn't needed.
> ejb-client dependencies should be placed in defaultLibBundleDir
> ---------------------------------------------------------------
>
> Key: MEAR-85
> URL: http://jira.codehaus.org/browse/MEAR-85
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
> Affects Versions: 2.3.1
> Reporter: James Olsen
> Priority: Minor
>
> ejb-client jars should be placed in the defaultLibBundleDir when specified.
> They're just standard jar dependencies not J2EE artifacts so should be
> treated the same as other jars. They're currently being placed in the root
> directory.
> A workaround is to add an ejbClientModule entry to override the bundleDir:
> <modules>
> <ejbClientModule>
> <groupId>...</groupId>
> <artifactId>...</artifactId>
> <bundleDir>lib</bundleDir>
> </ejbClientModule>
> </modules>
--
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
