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

John Casey updated MASSEMBLY-504:
---------------------------------

    Description: 
*NOTE:* This will only happen in very specific cases! See comments and linked 
issue.

In a reactor, there are 4 modules A, B, C and D.
 * A and B depends on C
 * D depends 
 ** on B
 ** on A due to a profile.

When making an assembly from D
 * including A 
 * excluding B
 * using transitive dependencies

{noformat}
  <formats>
    <format>dir</format>
  </formats>
  <includeBaseDirectory>false</includeBaseDirectory>  
  <dependencySets>
    <dependencySet>
      <useTransitiveDependencies>true</useTransitiveDependencies>
      <useTransitiveFiltering>true</useTransitiveFiltering>
      <includes>
        <include>example:a</include>
      </includes>
      <excludes>
        <exclude>example:b</exclude>
      </excludes>
    </dependencySet>
  </dependencySets>
</assembly>
{noformat}

C isn't in the result directory.

Remark: C is in the result directory if D depends on A normally.

  was:
In a reactor, there are 4 modules A, B, C and D.
 * A and B depends on C
 * D depends 
 ** on B
 ** on A due to a profile.

When making an assembly from D
 * including A 
 * excluding B
 * using transitive dependencies

{noformat}
  <formats>
    <format>dir</format>
  </formats>
  <includeBaseDirectory>false</includeBaseDirectory>  
  <dependencySets>
    <dependencySet>
      <useTransitiveDependencies>true</useTransitiveDependencies>
      <useTransitiveFiltering>true</useTransitiveFiltering>
      <includes>
        <include>example:a</include>
      </includes>
      <excludes>
        <exclude>example:b</exclude>
      </excludes>
    </dependencySet>
  </dependencySets>
</assembly>
{noformat}

C isn't in the result directory.

Remark: C is in the result directory if D depends on A normally.

        Summary: Transitive dependencies missing when two deps rely on them, 
but one of the deps is excluded  (was: Transitive dependencies of a dependency 
added by a profile aren't taken into account)

> Transitive dependencies missing when two deps rely on them, but one of the 
> deps is excluded
> -------------------------------------------------------------------------------------------
>
>                 Key: MASSEMBLY-504
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-504
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2-beta-5
>            Reporter: Guillaume Eyroulet
>         Attachments: maven-assembly-example.zip
>
>
> *NOTE:* This will only happen in very specific cases! See comments and linked 
> issue.
> In a reactor, there are 4 modules A, B, C and D.
>  * A and B depends on C
>  * D depends 
>  ** on B
>  ** on A due to a profile.
> When making an assembly from D
>  * including A 
>  * excluding B
>  * using transitive dependencies
> {noformat}
>   <formats>
>     <format>dir</format>
>   </formats>
>   <includeBaseDirectory>false</includeBaseDirectory>  
>   <dependencySets>
>     <dependencySet>
>       <useTransitiveDependencies>true</useTransitiveDependencies>
>       <useTransitiveFiltering>true</useTransitiveFiltering>
>       <includes>
>         <include>example:a</include>
>       </includes>
>       <excludes>
>               <exclude>example:b</exclude>
>       </excludes>
>     </dependencySet>
>   </dependencySets>
> </assembly>
> {noformat}
> C isn't in the result directory.
> Remark: C is in the result directory if D depends on A normally.

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