the dependency report ignores mirrors

Details

Type: Bug
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: 2.1.1
Fix Version/s: 2.2
Component/s: dependencies
Labels:
None

Description

The dependencies report takes forever and running debug i can see it's hitting the same repos over and over and bypassing my repository manager.

Options
- Sort By Name
- Sort By Date
- Ascending
- Descending
- Download All

Attachments

log.log

07/Dec/10 3:23 AM

193 kB

Dominique Jean-Prost
MPIR-150.patch

04/Feb/10 6:33 AM

0.8 kB

Philipp Berger

Issue Links

is duplicated by

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

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

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Vincent Siveton added a comment - 04/Mar/09 1:55 PM

Do you mean an intranet repo or similar?

Show

Vincent Siveton added a comment - 04/Mar/09 1:55 PM Do you mean an intranet repo or similar?

Hide

Permalink

Julien HENRY added a comment - 31/Mar/09 4:50 AM

I have the same problem.

I have a corporate archiva mirror for central:

<mirror>
      <id>central</id>
      <mirrorOf>central</mirrorOf>
      <name>Central Mirror</name>
      <url>http://pic-java-nce.sud.mycompany.fr:8090/archiva/repository/central</url>
</mirror>

And also 2 additional repos declared in my pom.xml:

<repositories>
		<!-- Repositories Corporate  -->
		<repository>
			<id>mycompany.corporate.release</id>
			<name>mycompany Corporate Release Repository</name>
			<url>http://pic-java-nce.sud.mycompany.fr:8090/archiva/repository/mycompany.corporate.release</url>
			<releases>
				<enabled>true</enabled>
			</releases>
			<snapshots>
				<enabled>false</enabled>
			</snapshots>
		</repository>
		<repository>
			<id>mycompany.local.release</id>
			<name>mycompany Local Release Repository</name>
			<url>http://pic-java-nce.sud.mycompany.fr:8090/archiva/repository/release</url>
			<releases>
				<enabled>true</enabled>
			</releases>
			<snapshots>
				<enabled>false</enabled>
			</snapshots>
		</repository>
	</repositories>

Running:

mvn org.apache.maven.plugins:maven-project-info-reports-plugin:2.1.1:dependencies -X

Takes 3 minutes 37 seconds with lots of:

[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
http://repo1.maven.org/maven/ - Session: Opened
http://repo1.maven.org/maven/ - Session: Disconnecting
http://repo1.maven.org/maven/ - Session: Disconnected
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
http://people.apache.org/repo/m2-incubating-repository/ - Session: Opened
http://people.apache.org/repo/m2-incubating-repository/ - Session: Disconnecting
http://people.apache.org/repo/m2-incubating-repository/ - Session: Disconnected
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
http://repository.codehaus.org - Session: Opened
http://repository.codehaus.org - Session: Disconnecting
http://repository.codehaus.org - Session: Disconnected
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
http://repo1.maven.org/eclipse - Session: Opened
http://repo1.maven.org/eclipse - Session: Disconnecting
http://repo1.maven.org/eclipse - Session: Disconnected
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
http://repo1.maven.org/maven2 - Session: Opened
http://repo1.maven.org/maven2 - Session: Disconnecting
http://repo1.maven.org/maven2 - Session: Disconnected
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
http://ws.zones.apache.org/repository2 - Session: Opened
http://ws.zones.apache.org/repository2 - Session: Disconnecting
http://ws.zones.apache.org/repository2 - Session: Disconnected

Very blocking for me because some projects that use a lot of additional repositories have their build taking more than 1 hour instead of less than 2 minutes after disabling dependency report.

The only workaround for my IC platform is to lock down plugin version to 2.0.1.

If you need more debug informations, fell free to ask.

Show

Julien HENRY added a comment - 31/Mar/09 4:50 AM I have the same problem. I have a corporate archiva mirror for central:

<mirror>
      <id>central</id>
      <mirrorOf>central</mirrorOf>
      <name>Central Mirror</name>
      <url>http://pic-java-nce.sud.mycompany.fr:8090/archiva/repository/central</url>
</mirror>

And also 2 additional repos declared in my pom.xml:

<repositories>
		<!-- Repositories Corporate  -->
		<repository>
			<id>mycompany.corporate.release</id>
			<name>mycompany Corporate Release Repository</name>
			<url>http://pic-java-nce.sud.mycompany.fr:8090/archiva/repository/mycompany.corporate.release</url>
			<releases>
				<enabled>true</enabled>
			</releases>
			<snapshots>
				<enabled>false</enabled>
			</snapshots>
		</repository>
		<repository>
			<id>mycompany.local.release</id>
			<name>mycompany Local Release Repository</name>
			<url>http://pic-java-nce.sud.mycompany.fr:8090/archiva/repository/release</url>
			<releases>
				<enabled>true</enabled>
			</releases>
			<snapshots>
				<enabled>false</enabled>
			</snapshots>
		</repository>
	</repositories>

Running:

mvn org.apache.maven.plugins:maven-project-info-reports-plugin:2.1.1:dependencies -X

Takes 3 minutes 37 seconds with lots of:

[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
http://repo1.maven.org/maven/ - Session: Opened
http://repo1.maven.org/maven/ - Session: Disconnecting
http://repo1.maven.org/maven/ - Session: Disconnected
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
http://people.apache.org/repo/m2-incubating-repository/ - Session: Opened
http://people.apache.org/repo/m2-incubating-repository/ - Session: Disconnecting
http://people.apache.org/repo/m2-incubating-repository/ - Session: Disconnected
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
http://repository.codehaus.org - Session: Opened
http://repository.codehaus.org - Session: Disconnecting
http://repository.codehaus.org - Session: Disconnected
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
http://repo1.maven.org/eclipse - Session: Opened
http://repo1.maven.org/eclipse - Session: Disconnecting
http://repo1.maven.org/eclipse - Session: Disconnected
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
http://repo1.maven.org/maven2 - Session: Opened
http://repo1.maven.org/maven2 - Session: Disconnecting
http://repo1.maven.org/maven2 - Session: Disconnected
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
http://ws.zones.apache.org/repository2 - Session: Opened
http://ws.zones.apache.org/repository2 - Session: Disconnecting
http://ws.zones.apache.org/repository2 - Session: Disconnected

Very blocking for me because some projects that use a lot of additional repositories have their build taking more than 1 hour instead of less than 2 minutes after disabling dependency report. The only workaround for my IC platform is to lock down plugin version to 2.0.1. If you need more debug informations, fell free to ask.

Hide

Permalink

Julien HENRY added a comment - 24/Jul/09 1:54 AM

Is this bug a duplicate of (now resolved) ~~MPIR-160~~?

Show

Julien HENRY added a comment - 24/Jul/09 1:54 AM Is this bug a duplicate of (now resolved) ~~MPIR-160~~?

Hide

Permalink

Justin Smith added a comment - 30/Jul/09 5:33 PM

I am getting the same symptoms on 2.2.0 r788681... Using artifactory on the intranet here.

Show

Justin Smith added a comment - 30/Jul/09 5:33 PM I am getting the same symptoms on 2.2.0 r788681... Using artifactory on the intranet here.

Hide

Permalink

Mark Anderson added a comment - 06/Oct/09 5:45 PM - edited

We too are experiencing this issue, with Maven 2.2.1 on a new Linux build server in our environment. Our main Linux build server (same configuration as far as we can tell) does not experience the issue, nor have we seen the issue on Windows developer environments we use.

We have an EAR build that usually takes about 47 seconds to complete on unaffected servers. When affected by this issue, the build time increases to nearly 8 minutes.

The site goal starts normally, then we get a 3 minute and 13 second delay on one of our modules, followed by (not sure this is related):

build	06-Oct-2009 14:27:36	[WARNING] The repository url 'https://maven-repository.dev.java.net/nonav/repository' 
is invalid - Repository 'java.net' will be blacklisted.

and then a LOT of the following messages for dozens of repositories, taking up almost another 3 minutes of the site generation for the different modules in our EAR build.

build	06-Oct-2009 14:27:43	[DEBUG] Using Wagon implementation lightweight from default mapping for protocol http
build	06-Oct-2009 14:27:43	[DEBUG] Checking for pre-existing User-Agent configuration.
build	06-Oct-2009 14:27:43	[DEBUG] Adding User-Agent configuration.
build	06-Oct-2009 14:27:43	http://repo1.maven.org/maven2 - Session: Opened  
build	06-Oct-2009 14:27:43	http://repo1.maven.org/maven2 - Session: Disconnecting  
build	06-Oct-2009 14:27:43	http://repo1.maven.org/maven2 - Session: Disconnected
...

Manually setting the version of the maven-project-info-reports-plugin to version 2.0.1 works around the issue for us too.

Our Maven install is basic with no mirrors or artifactory configurations. We are behind a corporate proxy that is configured in settings.xml.

Show

Mark Anderson added a comment - 06/Oct/09 5:45 PM - edited We too are experiencing this issue, with Maven 2.2.1 on a new Linux build server in our environment. Our main Linux build server (same configuration as far as we can tell) does not experience the issue, nor have we seen the issue on Windows developer environments we use. We have an EAR build that usually takes about 47 seconds to complete on unaffected servers. When affected by this issue, the build time increases to nearly 8 minutes. The site goal starts normally, then we get a 3 minute and 13 second delay on one of our modules, followed by (not sure this is related):

build	06-Oct-2009 14:27:36	[WARNING] The repository url 'https://maven-repository.dev.java.net/nonav/repository' 
is invalid - Repository 'java.net' will be blacklisted.

and then a LOT of the following messages for dozens of repositories, taking up almost another 3 minutes of the site generation for the different modules in our EAR build.

build	06-Oct-2009 14:27:43	[DEBUG] Using Wagon implementation lightweight from default mapping for protocol http
build	06-Oct-2009 14:27:43	[DEBUG] Checking for pre-existing User-Agent configuration.
build	06-Oct-2009 14:27:43	[DEBUG] Adding User-Agent configuration.
build	06-Oct-2009 14:27:43	http://repo1.maven.org/maven2 - Session: Opened  
build	06-Oct-2009 14:27:43	http://repo1.maven.org/maven2 - Session: Disconnecting  
build	06-Oct-2009 14:27:43	http://repo1.maven.org/maven2 - Session: Disconnected
...

Manually setting the version of the maven-project-info-reports-plugin to version 2.0.1 works around the issue for us too. Our Maven install is basic with no mirrors or artifactory configurations. We are behind a corporate proxy that is configured in settings.xml.

Hide

Permalink

Lukas Laag added a comment - 10/Dec/09 6:38 AM - edited

The workaround consisting in locking down the plugin to version 2.0.1 only works partially for me (works for the "Dependencies" report but not for the "Project License" report)

Show

Lukas Laag added a comment - 10/Dec/09 6:38 AM - edited The workaround consisting in locking down the plugin to version 2.0.1 only works partially for me (works for the "Dependencies" report but not for the "Project License" report)

Hide

Permalink

Philipp Berger added a comment - 04/Feb/10 6:33 AM

Here's a patch that i think might fix the issue. It is to be applied to version 2.2-SNAPSHOT in svn trunk (revision 906443).

Show

Philipp Berger added a comment - 04/Feb/10 6:33 AM Here's a patch that i think might fix the issue. It is to be applied to version 2.2-SNAPSHOT in svn trunk (revision 906443).

Hide

Permalink

Olivier Lamy added a comment - 13/May/10 4:07 PM

fixed rev 944014
Thanks!

Show

Olivier Lamy added a comment - 13/May/10 4:07 PM fixed rev 944014 Thanks!

Hide

Permalink

Prashant Bhate added a comment - 13/Jul/10 10:15 AM

Thanks a lot for this patch, Now site deployment would be much quicker.

it would be nice if url.openStream();

InputStream in =null;

try
{
  in = url.openStream();

can be replaced with

//Define constant TIMEOUT with pre set timeout
 
  InputStream in =null;

  try
  {
   URLConnection conn = url.openConnection();
   conn.setConnectTimeout(TIMEOUT);
   conn.setReadTimeout(TIMEOUT);
   in = conn.getInputStream();

url.openStream(); is a blocking call that makes caller wait forever

Show

Prashant Bhate added a comment - 13/Jul/10 10:15 AM Thanks a lot for this patch, Now site deployment would be much quicker. it would be nice if url.openStream();

InputStream in =null;

try
{
  in = url.openStream();

can be replaced with

//Define constant TIMEOUT with pre set timeout
 
  InputStream in =null;

  try
  {
   URLConnection conn = url.openConnection();
   conn.setConnectTimeout(TIMEOUT);
   conn.setReadTimeout(TIMEOUT);
   in = conn.getInputStream();

url.openStream(); is a blocking call that makes caller wait forever

Hide

Permalink

Olivier Lamy added a comment - 13/Jul/10 4:21 PM

please open a new issue for this.
Thanks.

Show

Olivier Lamy added a comment - 13/Jul/10 4:21 PM please open a new issue for this. Thanks.

Hide

Permalink

Prashant Bhate added a comment - 15/Jul/10 6:51 PM

Hi,
Raised http://jira.codehaus.org/browse/MPIR-199

Cheers,
Prashant Bhate

Show

Prashant Bhate added a comment - 15/Jul/10 6:51 PM Hi, Raised http://jira.codehaus.org/browse/MPIR-199 Cheers, Prashant Bhate

Hide

Permalink

Dominique Jean-Prost added a comment - 07/Dec/10 3:22 AM

Well, I think I still meet the same problem.

My settings.xml :

<mirrors>
		<mirror>
			<mirrorOf>*</mirrorOf>
			<url>http://vsrigel:7001/archiva/repository/global</url>
			<id>everything-mirror</id>
		</mirror>
		
	</mirrors>

when I execute "c:\bin\apache-maven-2.2.1\bin\mvn project-info-reports:dependencies", the plugin hangs twice and displays :

[WARNING] The repository url 'http://repo1.maven.org/maven2' is invalid - Repository 'central' will be blacklisted.
[WARNING] The repository url 'http://svn.apache.org/maven-snapshot-repository' is invalid - Repository 'apache.snapshots' will be blacklisted.

I also get tons of
[DEBUG] Using mirror: http://vsrigel:7001/archiva/repository/global (id: everything-mirror)
[DEBUG] Using Wagon implementation lightweight from default mapping for protocol http
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
http://vsrigel:7001/archiva/repository/global - Session: Opened
http://vsrigel:7001/archiva/repository/global - Session: Disconnecting
http://vsrigel:7001/archiva/repository/global - Session: Disconnected

Please find my execution log as an attachment.
Should this bug be reopened ? Or am I wrong ?

Thank you
Dom

Show

Dominique Jean-Prost added a comment - 07/Dec/10 3:22 AM Well, I think I still meet the same problem. My settings.xml :

<mirrors>
		<mirror>
			<mirrorOf>*</mirrorOf>
			<url>http://vsrigel:7001/archiva/repository/global</url>
			<id>everything-mirror</id>
		</mirror>
		
	</mirrors>

when I execute "c:\bin\apache-maven-2.2.1\bin\mvn project-info-reports:dependencies", the plugin hangs twice and displays : [WARNING] The repository url 'http://repo1.maven.org/maven2' is invalid - Repository 'central' will be blacklisted. [WARNING] The repository url 'http://svn.apache.org/maven-snapshot-repository' is invalid - Repository 'apache.snapshots' will be blacklisted. I also get tons of [DEBUG] Using mirror: http://vsrigel:7001/archiva/repository/global (id: everything-mirror) [DEBUG] Using Wagon implementation lightweight from default mapping for protocol http [DEBUG] Checking for pre-existing User-Agent configuration. [DEBUG] Adding User-Agent configuration. http://vsrigel:7001/archiva/repository/global - Session: Opened http://vsrigel:7001/archiva/repository/global - Session: Disconnecting http://vsrigel:7001/archiva/repository/global - Session: Disconnected Please find my execution log as an attachment. Should this bug be reopened ? Or am I wrong ? Thank you Dom

Hide

Permalink

Dominique Jean-Prost added a comment - 07/Dec/10 3:23 AM

log that shows bug is still there in org.apache.maven.plugins:maven-project-info-reports-plugin:2.2:dependencies ?

Show

Dominique Jean-Prost added a comment - 07/Dec/10 3:23 AM log that shows bug is still there in org.apache.maven.plugins:maven-project-info-reports-plugin:2.2:dependencies ?

People

Assignee:

Olivier Lamy

Reporter:

Brian Fox

Vote (16)

Watch (19)

Dates

Created:

03/Mar/09 8:36 PM

Updated:

07/Dec/10 3:23 AM

Resolved:

13/May/10 4:07 PM