[
https://jira.codehaus.org/browse/MNG-5243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
S.Leske reopened MNG-5243:
--------------------------
Reopening, as the problem still occurs.
A complete test case is included (see attached dependency-bug.tgz), so I hope
this can be addressed.
> If a transitive dependency is missing, the error message makes it very hard
> to find out where it comes from
> -----------------------------------------------------------------------------------------------------------
>
> Key: MNG-5243
> URL: https://jira.codehaus.org/browse/MNG-5243
> Project: Maven 2 & 3
> Issue Type: Bug
> Reporter: S.Leske
> Priority: Minor
> Attachments: dependency-bug.tgz
>
>
> If a transitive dependency cannot be resolved during the build, the build
> fails (so far obviously OK). However, the error message printed does not
> indicate where the dependency came from. It may have been pulled in via
> several layers of transitive dependencies, in that case it is very difficult
> to figure out how it got included.
> Example:
> Project dependencies are: A -> B -> C. Error message during build of A, if C
> is missing from the repo:
> {noformat}
> [...]
> [WARNING] The POM for dependency-bug-test:C:jar:1 is missing, no
> dependency information available
> [INFO] -------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] -------------------------------------------
> [...]
> [ERROR] Failed to execute goal on project A: Could not resolve dependencies
> for project dependency-bug-test:A:jar:1:
> Failure to find dependency-bug-test:C:jar:1 in
> http://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of
> central has elapsed or updates are forced -> [Help 1]
> [...]
> {noformat}
> Note the error message gives no indication whatsoever that the missing C is
> required because B depends on it. With more complex dependencies, this makes
> tracking down the culprit very difficult.
> Also note that "mvn dependency:tree" does not help in this case, because it
> fails with the same unhelpful error :-(.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
