maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Corridor Software Developer (JIRA)" <>
Subject [jira] Commented: (MEAR-85) ejb-client dependencies should be placed in defaultLibBundleDir
Date Sat, 03 Jan 2009 15:02:20 GMT


Corridor Software Developer commented on MEAR-85:

How about defaultEjbClientLibDir? Or even add the Bundle as well (a bit of a wasted word,
but for consistency).

In my case the classifier is working fine. But it would be nice if ejb-client was handled
without issue. We're up to eleven modules on the same project that require this btw.

> ejb-client dependencies should be placed in defaultLibBundleDir
> ---------------------------------------------------------------
>                 Key: MEAR-85
>                 URL:
>             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:
For more information on JIRA, see:


View raw message