[
https://issues.apache.org/jira/browse/MJAVADOC-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MJAVADOC-389.
-----------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> managed dependencies not used when resolving dependency sources
> ---------------------------------------------------------------
>
> Key: MJAVADOC-389
> URL: https://issues.apache.org/jira/browse/MJAVADOC-389
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.9.1
> Reporter: John Casey
> Assignee: John Casey
> Priority: Major
>
> I have a managed dependency in my POM that modifies a transitive dependency.
> When I build, and even when I use dependency:tree, the output is as I expect
> it to be.
> However, when I run the javadoc report with includeDependencySources=true it
> tries to download sources for the unmodified transitive dependency version,
> not my managed one.
> The problem is in ResourceResolver at line 346, where the
> resolveTransitively() call doesn't pass in the managed-version map from the
> project. I'll attach a failing test case as soon as I can set one up.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
