[
https://issues.apache.org/jira/browse/MNG-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130924#comment-15130924
]
Christian Schulte commented on MNG-5227:
----------------------------------------
See [Aether Bug 398572|https://bugs.eclipse.org/bugs/show_bug.cgi?id=398572].
{quote}
Pretty much all aspects of a dependency can be controlled via a
DependencyManager, but the optional flag not. *Pure oversight.*
{quote}
The optional flag is broken/useless if you cannot manage it. Managing
'optional' to 'true' is the same as excluding that dependency everywhere. In
dependency management you can omit the version. That's the missing 'global
exclude' feature. If you happen to depend on some project with dependencies
flagged optional, you can globally select them without having to care about the
version in dependency management. *Pure oversight.*
> The 'optional' flag of a dependency should be manageable.
> ---------------------------------------------------------
>
> Key: MNG-5227
> URL: https://issues.apache.org/jira/browse/MNG-5227
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 3.0.3
> Reporter: Christian Schulte
> Assignee: Christian Schulte
> Priority: Minor
> Fix For: 3.4.0
>
> Attachments: MNG-5227.patch, MNG-5227.patch
>
>
> {code}
> <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>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
