You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "S.Leske (JIRA)" <ji...@codehaus.org> on 2014/05/12 17:43:10 UTC

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

S.Leske created MNG-5632:
----------------------------

             Summary: Optional tag in dependencyManagement not inherited - disallow and/or document
                 Key: MNG-5632
                 URL: https://jira.codehaus.org/browse/MNG-5632
             Project: Maven 2 & 3
          Issue Type: Improvement
    Affects Versions: 3.2.1, 3.1.1
            Reporter: S.Leske
            Priority: Minor


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

{code}
<optional>true</optional>
{code}

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).



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)