[
https://issues.apache.org/jira/browse/MNG-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130874#comment-15130874
]
Christian Schulte commented on MNG-5227:
----------------------------------------
Please see the Aether bug this issue is linked to. It's not changing the way
dependency management works. It's just changing the order in which dependency
selection and dependency management is performed. Instead of first deciding to
select a dependency and then applying management (updating the selected
dependency), it needs to first apply management to a dependency to then use the
managed state to decide if that dependency is to be selected. So if you manage
the scope to test, a transitive dependency will correctly no longer be selected
and if you manage the optionality to 'true', a transitive dependency will also
correctly no longer be selected.
> 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)
