[MASSEMBLY-571] moduleSet dependencies processed incorrectly

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Not A Problem
• Affects Version/s: 2.2.1
• Component/s: moduleSet
• Environment: any
• Assignee: Kristian Rosenvold
• Reporter: Paul Green
• Created: 07/Sep/11 10:25
• Updated: 31/Jan/15 13:41
• Resolved: 04/Nov/14 02:26

Description

Following configuration:

        <moduleSet>
            <includes>
                <include>com.example:extra-hiper-app</include>
            </includes>
            <binaries>
                <outputFileNameMapping>my-app.${extension}</outputFileNameMapping>
                <outputDirectory>output/lib</outputDirectory>
                <unpack>false</unpack>

                <includeDependencies>true</includeDependencies>
                <dependencySets>
                    <dependencySet>
                        <outputFileNameMapping>${artifactId}-${version}.${extension}</outputFileNameMapping>
                    </dependencySet>
                </dependencySets>
            </binaries>
        </moduleSet>

Results in bunch of:

[INFO] lib/my-app-0.0.1.${extension} already added, skipping

with assembly plugin in version 2.2.1

NOTE: but it works correctly (and as expected with version: 2.2-beta-1)