[MASSEMBLY-672] unpack adds the name of the artifact in case of filtered unpack

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.4
• Assignee: Kristian Rosenvold
• Reporter: Tamas Cserveny
• Created: 06/Nov/13 11:04
• Updated: 06/Jan/16 20:01
• Resolved: 29/Oct/14 00:15

Description

In case I use unpack=true with unpackOptions.filtered=true, then the dependency will land in a file named after the "groupId/artifactId/type/classifier/version".

By removing the filtered tag, the dependency will be put into the right outputDirectory.

Example:

  <dependencySets>
    <dependencySet>
      <outputDirectory>/</outputDirectory>
      <includes>
        <include>groupId:artifactId:zip</include>
      </includes>
      <unpack>true</unpack>
      <unpackOptions>
        <excludes>
          <exclude>**/*.xml</exclude><!-- unpack will include those -->
          <exclude>**/*.cfg</exclude>
        </excludes>
      </unpackOptions>
      <useProjectArtifact>false</useProjectArtifact>
       <filtered>true</filtered>
    </dependencySet>
  </dependencySets>

Will generate a dir called "groupId.artifactId-2.0.0-SNAPSHOT.zip/".

The output directory is completely ignored in this case, if I would specify "X" inside, the above directory won't land in x instead it will land in the above generated dir.

Cheers,

Tamas

Issue Links

• duplicates: MASSEMBLY-533 Outputidrectory appended by dependencyset include name on filtered=true
• duplicates: MASSEMBLY-554 DependencySet unpackOptions 'filtered' causes unpack not to work
• duplicates: MASSEMBLY-579 Dependency-filename appended as subdirectory of outputDirectory of dependencySet when unpackOptions/filtered = true