Uploaded image for project: 'Maven Assembly Plugin'
  1. Maven Assembly Plugin
  2. MASSEMBLY-132

Assembly for multi-project ignoring specified scope

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • 2.1
    • 2.2-beta-1
    • None
    • None
    • All

    Description

      After converting my project to a multi-project, the assembly plugin fails to filter out dependency jars that have a scope other than runtime, even when the scope in the descriptor is explicitly provided. My dep.xml -

      <dependencySets>

      <dependencySet>

      <outputDirectory>mims-${version}/lib</outputDirectory>

      <unpack>false</unpack>

      <scope>runtime</scope>

      </dependencySet>

      </dependencySets>

      I even tried putting exclude statements in the <moduleSet/> <binaries/> section, but even that doesn't work. As a result, the assembly is littered with unnecessary jars such as junit.

      Attachments

        Activity

          People

            jdcasey John Dennis Casey
            vinod.p Vinod Panicker
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: