[ 
http://jira.codehaus.org/browse/MASSEMBLY-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=228828#action_228828
 ] 

Andy Webster commented on MASSEMBLY-362:
----------------------------------------

Using Maven 2.2.1 I got the same problem but resolved it as follows:

In pom.xml
{noformat} 
    <dependency>
        <groupId>mygroup</groupId>
        <artifactId>myartifact-ejb</artifactId>
        <version>myversion</version> 
        <type>ejb</type> 
        <classifier>client</classifier>
    </dependency>
{noformat} 

In assembly.xml
{noformat}
<include>mygroup:myartifact-ejb:*:client</include>
{noformat}

If there is no classifier, then the type can be ejb as normal. 

However, as I have a classifier (client) I have found that neither ejb nor jar 
work, but * does.

> Not able to include ejb-client artifact in jar-with-dependencies
> ----------------------------------------------------------------
>
>                 Key: MASSEMBLY-362
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-362
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2-beta-2
>            Reporter: Henrik Brautaset Aronsen
>
> The assembly:assembly target with jar-with-dependencies does not include my 
> ejb-client dependency.  The jar dependencies are included.  I've tried 
> specifiying my own assembly.xml, but the artifact isn't included nonetheless:
> assembly.xml:
> {code}<includes>
>    <include>mygroup:myartifact-ejb</include>
> </includes>
> {code}
> pom.xml:
> {code}<dependency>
>    <groupId>mygroup</groupId>
>    <artifactId>myartifact-ejb</artifactId>
>    <type>ejb-client</type>
> </dependency>
> {code}
> I've also tried {{mygroup:myartifact-ejb:*}}, 
> {{mygroup:myartifact-ejb:ejb-client}} and a couple of other combinations.  
> Maven still complains:
> {code}[WARNING] The following patterns were never triggered in this artifact 
> inclusion filter:
> o  'mygroup:myartifact-ejb'
> {code}

-- 
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

        

Reply via email to