[
https://issues.apache.org/jira/browse/MNG-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130835#comment-15130835
]
Joerg Schaible commented on MNG-5227:
-------------------------------------
I just reported MNG-1577, the patch was provided by [~ralphgoers] and
[~pschneider]. Personally I only cared about the version and scope management.
However, it looks wrong to me dropping the test scope and setting optional to
false should not matter for your changes. Do you have now a test case where you
set optional to true in the dependencyManagement section and set it explicitly
to false again in the dependencies?
> 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)
