[ 
http://jira.codehaus.org/browse/MPIR-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146805#action_146805
 ] 

Allor Dev commented on MPIR-137:
--------------------------------

The workaround does not work for me. I had to change 
maven-project-info-reports-plugin version to 2.0.

> Dependency Locations should work with an intranet repository and restricted 
> internet access
> -------------------------------------------------------------------------------------------
>
>                 Key: MPIR-137
>                 URL: http://jira.codehaus.org/browse/MPIR-137
>             Project: Maven 2.x Project Info Reports Plugin
>          Issue Type: Improvement
>          Components: dependencies
>    Affects Versions: 2.1
>         Environment: All environments, no internet access allowed, no 
> internet proxy configuration, intranet repository configured (Artifactory, 
> but it seems to happen with Archiva)
>            Reporter: Diego Parrilla
>            Priority: Minor
>
> We use Maven and Artifactory, and the PCs does not have direct internet 
> access allowed. Maven is configured to mirror the Artifactory repository. So, 
> all the users have to download their artifacts from the intranet repository.
> When launching the 'site' goal (mvn site), when generating the 'Dependencies' 
> report, it hangs for a long time until we get this error:
> [WARNING] The repository url 'XXXXXXXX' is invalid - Repository 'XXX' will be 
> blacklisted.
> It's possible to work around this problem disabling the parameter 
> 'dependencyLocationEnabled' in the maven-project-info-reports-plugin:
> <plugins>
> ...
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-project-info-reports-plugin</artifactId>
> <version>2.1</version>
> <configuration>
> <dependencyLocationEnabled>false</dependencyLocationEnabled>
> </configuration>
> <plugin>
> ...
> </plugins> 
> But I think the dependency locations should be solved using the information 
> stored in the intranet repository (in my case Artifactory). At this moment 
> the reports generated do not include the Dependency Location information.
> You can read this thread for a further description:
> http://www.nabble.com/Problem-with-Maven%2C-Hudson%2C-Archiva---Builds-take-very-long-td19158623.html#a19218823

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to