[ 
http://jira.codehaus.org/browse/MASSEMBLY-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John Casey closed MASSEMBLY-313.
--------------------------------

    Resolution: Won't Fix
      Assignee: John Casey

<attachmentClassifier> is used to reference attachments of the current project. 
If you want to access classified artifacts of some dependency, you should 
declare a dependency with the appropriate classifier, then make sure that 
dependency is referenced from your dependencySet.

> Honor <attachmentClassifier> also for transitive dependencies
> -------------------------------------------------------------
>
>                 Key: MASSEMBLY-313
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-313
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2-beta-1, 2.2-beta-2
>         Environment: all
>            Reporter: Thorsten Möller
>            Assignee: John Casey
>
> The plugin does not honor the <attachmentClassifier> for dependencies in 
> multi module projects but includes the default artifact even if an attached 
> artifact of the specified classifier is available. To illustrate this 
> consider the this excerpt from an assembly descriptor:
> <moduleSets>
>       <moduleSet>
>               <includes>
>                       <include>${pom.groupId}:common</include>
>                       <include>${pom.groupId}:core</include>
>               </includes>
>               <binaries>
>                       <includeDependencies>true</includeDependencies>
>                       <unpack>false</unpack>
>                       <outputDirectory>/lib</outputDirectory>
>                       <attachmentClassifier>jdk14</attachmentClassifier>
>               </binaries>
>       </moduleSet>
> </moduleSets>
> The current behavior resulting from this excerpt is that the plugin will 
> search for attached artifacts of "jdk14" only for the two modules "common" 
> and "core" but not for the dependencies of those modules, which will be 
> included in the assembly because "includeDependencies" is set to true. The 
> plugin should search for attached artifacts of the specified classifier 
> (jdk14) also for the (transitive) dependencies and take them if they exist. 
> If it can not find artifacts of the specified classifier it should fall back 
> to use the default artifact and write a warning message on the console saying 
> something like "No artifact "xyz" with classifier "xyz" found in "repos.xyz". 
> Including default instead."
> Regards,
> Thorsten

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