[MSHARED-437] maven-dependency-tree removes optional flag from managed dependencies

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: maven-dependency-tree-2.2
• Fix Version/s: maven-dependency-tree-3.0.1
• Component/s: maven-dependency-tree
• Assignee: Michael Osipov
• Reporter: Arlo Louis O'Keeffe
• Created: 19/Sep/15 09:21
• Updated: 10/May/17 09:17
• Resolved: 03/May/17 16:29

Description

Given the following pom the dependency tree looks like this

• com.mysema.querydsl:querydsl-core:jar:3.4.3:compile
  • com.google.guava:guava:jar:17.0:compile
  • com.google.code.findbugs:jsr305:jar:2.0.3:compile
  • com.mysema.commons:mysema-commons-lang:jar:0.2.4:compile
  • com.infradna.tool:bridge-method-annotation:jar:1.13:compile

You expect the entire tree to have the optional flag set to true. But sadly that's not the case. com.google.guava:guava and com.google.code.findbugs:jsr305 are optional = false.

I found that this is because they are managed dependencies (no difference whether imported or declared directly). When I use this pom it works.

There are some integration tests in this repository that demonstrate the issue. Checkout demonstrate-tree-bug branch and run "mvn verify". Now compare these files in target/it

• buck-bom-managed-optional-transitive-dependencies/target/BUCK
• buck-managed-optional-transitive-dependencies/target/BUCK
• buck-optional-transitive-dependencies/target/BUCK

The CI builds demonstrating the failure.

Let me know if I can help you reproduce the problem.

Issue Links

• relates to: MNG-5935 Optional true getting lost in managed dependencies when transitive
• relates to: MNG-6228 Optionality not displayed in dependency tree when run in debug mode