maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pablo Graña (JIRA) <>
Subject [jira] Commented: (MPIR-137) Dependency Locations should work with an intranet repository and restricted internet access
Date Fri, 26 Sep 2008 17:28:45 GMT


Pablo Graña commented on MPIR-137:

The workaround does not work for me either.
As an additional note, I added:
<dependencyDetailsEnabled>false</dependencyDetailsEnabled> (I figured it had something
to do with this because the doc says that this param is ignored in offilne mode). But build
failed with:

[INFO] ------------------------------------------------------------------------
[INFO] Error during page generation

Embedded error: Error rendering Maven report: Error on line -1 of document  : Premature end
of file. Nested exception: Premature end of file.
[INFO] ------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error during page generation
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(

> Dependency Locations should work with an intranet repository and restricted internet
> -------------------------------------------------------------------------------------------
>                 Key: MPIR-137
>                 URL:
>             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:

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message