Maven 2.x Project Info Reports Plugin

Generation of HTML dependency report takes a long time due to accessing repositories not specified in pom

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Duplicate
  • Affects Version/s: 2.1
  • Fix Version/s: 2.2
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

Only repositories mentioned in pom.xml should be taken into consideration.
e.g.
Debug of build states
[INFO] Generating "Dependencies" report.
http://tomcat.apache.org/dev/dist/m2-repository - Session: Opened
http://tomcat.apache.org/dev/dist/m2-repository - Session: Disconnecting
http://tomcat.apache.org/dev/dist/m2-repository - Session: Disconnected

even if only a local repository/pluginrepository is defined in pom
So the side generation spends about 5 minutes to generate the report connecting to various repositories several times...

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.

Improvement - An improvement or enhancement to an existing feature or task. MPIR-137 Dependency Locations should work with an intranet repository and restricted internet access

  • 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
Brian Fox added a comment -

The dependency plugin doesn't manufacture repositories, chances are one of your dependencies includes the repositories in their pom. Not obeying them would lead to missing dependencies.

Show
Brian Fox added a comment - The dependency plugin doesn't manufacture repositories, chances are one of your dependencies includes the repositories in their pom. Not obeying them would lead to missing dependencies.
Hide
Permalink
EJ Ciramella added a comment -

What's the easiest way to detect this?

Some dependencies have a slew of dependencies as well.

Show
EJ Ciramella added a comment - What's the easiest way to detect this? Some dependencies have a slew of dependencies as well.
Hide
Permalink
Benjamin Bentmann added a comment -

[INFO] Generating "Dependencies" report.

This is generated by project-info-reports:dependencies. This goals can be configured or even completely disabled, see Run Selective Reports.

Show
Benjamin Bentmann added a comment - [INFO] Generating "Dependencies" report. This is generated by project-info-reports:dependencies . This goals can be configured or even completely disabled, see Run Selective Reports .
Hide
Permalink
EJ Ciramella added a comment -

While that's great - that means I need to pick and choose which projects (out of about 200) can and/or can't run this report.

Being able to detect which dependency has its own repository listed would be VERY helpful. Maven must know the dependency it's working on when it's spitting out that session info, too bad it couldn't prefix that message with the dependency information.

Show
EJ Ciramella added a comment - While that's great - that means I need to pick and choose which projects (out of about 200) can and/or can't run this report. Being able to detect which dependency has its own repository listed would be VERY helpful. Maven must know the dependency it's working on when it's spitting out that session info, too bad it couldn't prefix that message with the dependency information.

People

  • Assignee:
    Unassigned
    Reporter:
    Michael Hinterseher
Vote (1)
Watch (3)

Dates

  • Created:
    Updated:
    Resolved: