Uploaded image for project: 'Drools'
  1. Drools
  2. DROOLS-850

All maven assemblies must use <useTransitiveFiltering>true</> for every <dependencySet>

    XMLWordPrintable

Details

    • Task
    • Resolution: Unresolved
    • Minor
    • None
    • None
    • None
    • None
    • NEW
    • NEW

    Description

      When the assemblies were originally written, this option wasn't available yet. Because don't use it, we have been doing <excludes> for transitive dependencies, which have being going stale/incorrect as we've been upgrading dependency versions. it's a mess. The only sane thing to do is to use this option everywhere. As they admit, it should be the default but they couldn't:

      "<useTransitiveFiltering> Determines whether the include/exclude patterns in this dependency set will be applied to the transitive path of a given artifact. If true, and the current artifact is a transitive dependency brought in by another artifact which matches an inclusion or exclusion pattern, then the current artifact has the same inclusion/exclusion logic applied to it as well. By default, this value is false, in order to preserve backward compatibility with version 2.1. This means that includes/excludes only apply directly to the current artifact, and not to the transitive set of artifacts which brought it in. (Since 2.2-beta-1) "

      See
      https://maven.apache.org/plugins/maven-assembly-plugin/assembly.html#class_dependencySet

      Attachments

        Activity

          People

            Unassigned Unassigned
            gdesmet@redhat.com Geoffrey De Smet (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: