[MNG-5227] The 'optional' flag of a dependency should be manageable.

• Type: New Feature
• Status: Reopened
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 3.0.3
• Fix Version/s: 4.0.x-candidate
• Component/s: Artifacts and Repositories
• Assignee: Unassigned
• Reporter: Christian Schulte
• Created: 16/Jan/12 14:24
• Updated: 12/May/23 09:16

Description

<dependencyManagement>
  <dependencies>
    <dependency>
      <groupId>groupId</groupId>
      <artifactId>artifactId</artifactId>
      <version>version</version>
      <optional>false</optional> <!-- Ignored by Maven 2 & 3 in dependency management. -->
    </dependency>
  </dependencies>
</dependencyManagement>

Issue Links

• causes: HIVE-27338 JDBC drivers are transitively inherited although declared optional
• is blocked by: MRESOLVER-9 DefaultDependencyCollector does not correctly handle dependency management
• is depended upon by: MNG-5935 Optional true getting lost in managed dependencies when transitive
• is duplicated by: MNG-5632 Optional tag in dependencyManagement not inherited - disallow and/or document
• is required by: MNG-6139 Addition of command line option 'legacy-dependency-management'.
• relates to: MNG-5600 Dependency management import should support exclusions.
• relates to: MNG-2984 Allow more control around the configuration and use of optional dependencies
• supercedes: MNG-4600 [regression] Optional flag from dependency management applied to dependencies
• supercedes: MNG-1977 Global dependency exclusions
• supercedes: MNG-5959 Can maven provide a features that exclude dependency gloablly
• mentioned in: Page Loading...