[
http://jira.codehaus.org/browse/MPIR-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=193783#action_193783
]
Mark Anderson edited comment on MPIR-150 at 10/6/09 5:52 PM:
-------------------------------------------------------------
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):
{code}
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.
{code}
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.
{code}
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
...
{code}
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.
was (Author: marka):
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):
{code}
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.
{code}
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.
{code}
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
...
{code}
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.
> the dependency report ignores mirrors
> -------------------------------------
>
> Key: MPIR-150
> URL: http://jira.codehaus.org/browse/MPIR-150
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
> Affects Versions: 2.1.1
> Reporter: Brian Fox
>
> 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.
--
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
