[MNG-5632] Optional tag in dependencyManagement not inherited - disallow and/or document

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 3.1.1, 3.2.1
• Assignee: Unassigned
• Reporter: Sebastian Leske
• Created: 12/May/14 10:42
• Updated: 27/Jan/16 02:28
• Resolved: 27/Jan/16 02:28

Description

As explained in MNG-1630 adn MNG-4600, specifying

<optional>true</optional>

in dependencyManagement has no effect. "optional" only takes effect when specified directly in the "dependencies" section of the POM.

However, this is not documented anywhere, and rather unexpected, because both version and scope can be set from dependencyManagement.

If the current behaviour is intentional, it should be documented. Ideally, Maven should also disallow the use of "<optional>" in dependencyManagement (or at least issue a warning).

Issue Links

• duplicates: MNG-5227 The 'optional' flag of a dependency should be manageable.
• relates to: MNG-1630 Optional tag in dependencyManagement is not inherited in the children projects
• relates to: MNG-4600 [regression] Optional flag from dependency management applied to dependencies