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

2-nd <exclude> element of <dependencySets>:<excludes> doesn't work

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.2-beta-1
    • 2.2-beta-2
    • None
    • None
    • Patch

    Description

      I suppose that order of dependencySets:excludes:exclude doesn't make sense.
      But it seems that the plugin has a bug – 2-nd <exclude> element of <dependencySets>:<excludes> doesn't work at all!

      Having such a dependencySet
      <dependencySet>
      <unpack>false</unpack>
      <excludes>
      <exclude>org.eclipse.update.*</exclude>
      <exclude>org.eclipse.equinox.http.*</exclude>
      </excludes>
      </dependencySet>

      I receive warning about
      [WARNING] The following patterns were never triggered in this artifact exclusion filter:
      o 'org.eclipse.equinox.http.*'

      When I change the order of exclude elements
      <dependencySet>
      <unpack>false</unpack>
      <excludes>
      <exclude>org.eclipse.equinox.http.*</exclude>
      <exclude>org.eclipse.update.*</exclude>
      </excludes>
      </dependencySet>

      I receive warning about
      [WARNING] The following patterns were never triggered in this artifact exclusion filter:
      o 'org.eclipse.update.*'

      So, as you can see the both exclude patterns are workable, but 2-nd one doesn't work independently of the element order.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            jdcasey John Dennis Casey
            viy Eugene Voytitsky
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment