[ 
https://jira.codehaus.org/browse/MPIR-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317930#comment-317930
 ] 

Hannes Kogler edited comment on MPIR-251 at 1/24/13 5:52 AM:
-------------------------------------------------------------

I got the same error messages too. (Maven version 3.0.4; Plugin versions: 
maven-site-plugin3.2 & maven-project-info-reports-plugin 2.6)

Hoping that there is anybody who creates a bugfix for it!

A suitable workaround if waiting for a bugfix is not a eal option, just try to 
config the maven-project-info-reports-plugin with less message details:
{code:title=Bar.java|borderStyle=solid}
        <reporting>
                <plugins> ...
                        <plugin>
                                <groupId>org.apache.maven.plugins</groupId>
                                
<artifactId>maven-project-info-reports-plugin</artifactId>
                                <version>2.6</version>
                                <configuration>
                                        
<dependencyDetailsEnabled>false</dependencyDetailsEnabled>
                                        
<dependencyLocationsEnabled>false</dependencyLocationsEnabled>
                                </configuration>
                        </plugin>
                        ...
                </plugins>
        </reporting>
{code} 
it works for me!
                
      was (Author: ntshko):
    I got the same error messages too. (Maven version 3.0.4; Plugin versions: 
maven-site-plugin3.2 & maven-project-info-reports-plugin 2.6)

Hoping that there is anybody who creates a bugfix for it!

A suitable workaround if waiting for a bugfix is not a eal option, just try to 
config the maven-project-info-reports-plugin with less message details:
        <reporting>
                <plugins> ...
                        <plugin>
                                <groupId>org.apache.maven.plugins</groupId>
                                
<artifactId>maven-project-info-reports-plugin</artifactId>
                                <version>2.6</version>
                                <configuration>
                                        
<dependencyDetailsEnabled>false</dependencyDetailsEnabled>
                                        
<dependencyLocationsEnabled>false</dependencyLocationsEnabled>
                                </configuration>
                        </plugin>
                        ...
                </plugins>
        </reporting>

it works for me!
                  
> Artifact ###### has no file error regression.
> ---------------------------------------------
>
>                 Key: MPIR-251
>                 URL: https://jira.codehaus.org/browse/MPIR-251
>             Project: Maven 2.x Project Info Reports Plugin
>          Issue Type: Bug
>          Components: dependencies
>    Affects Versions: 2.5
>            Reporter: Ian Brandt
>            Priority: Minor
>         Attachments: 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to