[
https://issues.apache.org/jira/browse/MPIR-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15071978#comment-15071978
]
Michael Osipov commented on MPIR-251:
-------------------------------------
Guys, I think I have found the bug here. The {{DepenenciesRenderer}} has a
method {{hasSealed}} which instruct the {{RepositoryUtils}} to resolve entire
dependency tree down to {{Files}}. At the first file having a sealed
information that resolution is stopped. This means that the remeining have no
{{Files}} attached. I will break up that method in two, {{resolve}} and a dumb
{{hasSealed}}.
> Artifact ###### has no file error regression.
> ---------------------------------------------
>
> Key: MPIR-251
> URL: https://issues.apache.org/jira/browse/MPIR-251
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
> Affects Versions: 2.5
> Reporter: Ian Brandt
> Priority: Minor
> Attachments: pom.xml, pom.xml
>
>
> It appears that MPIR-158 has regressed. I'm seeing the same exact issue in
> 2.5 with Maven 3.0.4:
> {noformat}
> [INFO] Generating "Dependencies" report ---
> maven-project-info-reports-plugin:2.5
> [ERROR] Artifact: com.sun:tools:jar:1.5.0 has no file.
> [ERROR] Artifact: com.thoughtworks.xstream:xstream:jar:1.3 has no file.
> [ERROR] Artifact: commons-beanutils:commons-beanutils:jar:1.8.0 has no file.
> [ERROR] Artifact: commons-cli:commons-cli:jar:1.1 has no file.
> [ERROR] Artifact: commons-codec:commons-codec:jar:1.3 has no file.
> [ERROR] Artifact: commons-collections:commons-collections:jar:3.2.1 has no
> file.
> [ERROR] Artifact: commons-digester:commons-digester:jar:2.0 has no file.
> [ERROR] Artifact: commons-fileupload:commons-fileupload:jar:1.2.2 has no file.
> ...{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
