[
http://jira.codehaus.org/browse/MEAR-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143993#action_143993
]
Bryan Loofbourrow commented on MEAR-85:
---------------------------------------
| I could add a flag to copy ejbClient artifacts in the defaultLibBundleDir.
I'll take the liberty of replying with respect to my use case, described in my
earlier comment, even though your question was addressed to James Olsen.
As long as the flag applied to all ejbClient artifacts to be packaged in the
ear, including the ones pulled in by transitive dependencies, it sounds as
though it would fully address the use case that I have. Your proposal of a flag
is probably better than mine of a second Dir parameter, given that there is
probably no need to ever specify a distinct destination directory for ejbClient
artifacts. There's merely a need to piggyback on the destination directory
already specified.
> 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
> Assignee: Stephane Nicoll
> Priority: Minor
> Fix For: 2.3.2
>
>
> 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
