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

DpendencySet doesn't work anymore when taken from executedProject

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • 2.2
    • 2.2-beta-1
    • None
    • None
    • maven 2.0.4

    Description

      One of my project build just broke after an upgrade to the latest plugins.

      assembly contains:

      <dependencySets>
      <dependencySet>
      <outputDirectory>lib</outputDirectory>
      <unpack>false</unpack>
      <scope>runtime</scope>
      </dependencySet>

      If I add a logging to the DirectoryMojo class I can see that no dependencies are seen for the project.

      + getLog().debug( "DependencySet[" + output + "]" + " allDependencies: " + allDependencyArtifacts.size()
      + + " filtered: " + dependencyArtifacts.size() );
      +

      [INFO] [assembly:directory]
      [...]
      [DEBUG] DependencySet[ubd-1.0.1-SNAPSHOT/lib/] dir perms: 40755 file perms: 100644
      [DEBUG] DependencySet[ubd-1.0.1-SNAPSHOT/lib/] allDependencies: 0 filtered: 0
      [...]

      If I force the plugin to use the original project (not the executedProject), assembly works again (see patch).

      As such, this issue very similar to the MCLIRR-2 one encountered by Vincent.

      Attachments

        1. patch.diff
          1 kB
          Jerome Lacoste

        Activity

          People

            jdcasey John Dennis Casey
            lacostej Jerome Lacoste
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: