Maven 2.x Project Info Reports Plugin

Dependency Locations should work with an intranet repository and restricted internet access

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Duplicate
  • Affects Version/s: 2.1
  • Fix Version/s: 2.2
  • Component/s: dependencies
  • Labels:
    None
  • Environment:
    All environments, no internet access allowed, no internet proxy configuration, intranet repository configured (Artifactory, but it seems to happen with Archiva)
  • Number of attachments :
    0

Description

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

Issue Links

duplicates

Bug - A problem which impairs or prevents the functions of the product. MPIR-150 the dependency report ignores mirrors

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
is duplicated by

Improvement - An improvement or enhancement to an existing feature or task. MPIR-177 Generation of HTML dependency report takes a long time due to accessing repositories not specified in pom

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Allor Dev added a comment -

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

Show
Allor Dev added a comment - The workaround does not work for me. I had to change maven-project-info-reports-plugin version to 2.0.
Hide
Permalink
Pablo Graņa added a comment -

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:

[ERROR] BUILD ERROR
[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(DefaultLifecycleExecutor.java:564)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
.
.
.

Show
Pablo Graņa added a comment - 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: [ERROR] BUILD ERROR [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(DefaultLifecycleExecutor.java:564) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) . . .
Hide
Permalink
Pablo Graņa added a comment -

About my post ....

I just did mvn clean -> mvn site (instead of mvn clean site) and, it does not throw the stack trace. But still freezes for a long time Generating "Dependencies" report.

I guess I'll have to go to 2.0.1 ....

Show
Pablo Graņa added a comment - About my post .... I just did mvn clean -> mvn site (instead of mvn clean site) and, it does not throw the stack trace. But still freezes for a long time Generating "Dependencies" report. I guess I'll have to go to 2.0.1 ....
Hide
Permalink
Adrian added a comment -

FYI there's an error on the first post : element 'dependencyLocationEnabled' should be renamed 'dependencyLocationsEnabled' (missing s).

I was having the same pb during Generating "Dependencies" report.

I've added both dependencyLocationsEnabled and dependencyDetailsEnabled and it worked. No more freezing.

Here's my config snippet :
<reporting>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-project-info-reports-plugin</artifactId>
<configuration>
<dependencyLocationsEnabled>false</dependencyLocationsEnabled>
<dependencyDetailsEnabled>false</dependencyDetailsEnabled>
</configuration>
</plugin>
</plugins>
</reporting>

Show
Adrian added a comment - FYI there's an error on the first post : element 'dependencyLocationEnabled' should be renamed 'dependencyLocationsEnabled' (missing s). I was having the same pb during Generating "Dependencies" report. I've added both dependencyLocationsEnabled and dependencyDetailsEnabled and it worked. No more freezing. Here's my config snippet : <reporting> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-project-info-reports-plugin</artifactId> <configuration> <dependencyLocationsEnabled>false</dependencyLocationsEnabled> <dependencyDetailsEnabled>false</dependencyDetailsEnabled> </configuration> </plugin> </plugins> </reporting>
Hide
Permalink
Vincent Siveton added a comment -

The report uses the repositories defined in the pom dependencies. For instance, you could have the following 

[WARNING] The repository url 'http://snapshots.maven.codehaus.org/maven2' is invalid - Repository 'snapshots' will be blacklisted.

It is due because this repo is defined in an old version of Plexus's pom.

Using an intranet repository will produce the same error I guess.

Show
Vincent Siveton added a comment - The report uses the repositories defined in the pom dependencies. For instance, you could have the following [WARNING] The repository url 'http://snapshots.maven.codehaus.org/maven2' is invalid - Repository 'snapshots' will be blacklisted. It is due because this repo is defined in an old version of Plexus's pom. Using an intranet repository will produce the same error I guess.
Hide
Permalink
Niels Bo Andersen added a comment -

This issue also affects the use of Artifactory version 2.0.5, and possibly older. I've recently upgraded from v. 1.2.5, and I am now getting this error.

The reason for this is, that the plugin seems to request the base URL of the repository, i.e. http://artifactoryserver/artifactory/repo, without a trailing slash.
Artifactory version 1.2.5 returned a valid response to this request, but the new version returns a 404. Everything below the base URL is OK, and the rest of the build uses the Artifactory server without any problems.

If there is a requirement, that a repository should reply to the base URL, then this is of course a bug in Artifactory, but if there is no such requirement, this issue should be marked as a bug, not an improvement.

Show
Niels Bo Andersen added a comment - This issue also affects the use of Artifactory version 2.0.5, and possibly older. I've recently upgraded from v. 1.2.5, and I am now getting this error. The reason for this is, that the plugin seems to request the base URL of the repository, i.e. http://artifactoryserver/artifactory/repo , without a trailing slash. Artifactory version 1.2.5 returned a valid response to this request, but the new version returns a 404. Everything below the base URL is OK, and the rest of the build uses the Artifactory server without any problems. If there is a requirement, that a repository should reply to the base URL, then this is of course a bug in Artifactory, but if there is no such requirement, this issue should be marked as a bug, not an improvement.

People

  • Assignee:
    Olivier Lamy
    Reporter:
    Diego Parrilla
Vote (16)
Watch (16)

Dates

  • Created:
    Updated:
    Resolved: