You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Hinterseher (JIRA)" <ji...@codehaus.org> on 2008/11/19 16:38:41 UTC
[jira] Created: (MDEP-189) Generation of HTML dependency report
takes a long time due to accessing repositories not specified in pom
Generation of HTML dependency report takes a long time due to accessing repositories not specified in pom
---------------------------------------------------------------------------------------------------------
Key: MDEP-189
URL: http://jira.codehaus.org/browse/MDEP-189
Project: Maven 2.x Dependency Plugin
Issue Type: Improvement
Affects Versions: 2.0
Reporter: Michael Hinterseher
Assignee: Brian Fox
Priority: Minor
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...
--
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
[jira] Commented: (MPIR-177) Generation of HTML dependency report
takes a long time due to accessing repositories not specified in pom
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPIR-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197321#action_197321 ]
Benjamin Bentmann commented on MPIR-177:
----------------------------------------
bq. [INFO] Generating "Dependencies" report.
This is generated by [project-info-reports:dependencies|http://maven.apache.org/plugins/maven-project-info-reports-plugin/dependencies-mojo.html]. This goals can be configured or even completely disabled, see [Run Selective Reports|http://maven.apache.org/plugins/maven-project-info-reports-plugin/examples/selective-project-info-reports.html].
> Generation of HTML dependency report takes a long time due to accessing repositories not specified in pom
> ---------------------------------------------------------------------------------------------------------
>
> Key: MPIR-177
> URL: http://jira.codehaus.org/browse/MPIR-177
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Improvement
> Affects Versions: 2.1
> Reporter: Michael Hinterseher
> Assignee: Brian Fox
> Priority: Minor
>
> 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...
--
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
[jira] Updated: (MPIR-177) Generation of HTML dependency report
takes a long time due to accessing repositories not specified in pom
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPIR-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MPIR-177:
-----------------------------------
Assignee: (was: Brian Fox)
> Generation of HTML dependency report takes a long time due to accessing repositories not specified in pom
> ---------------------------------------------------------------------------------------------------------
>
> Key: MPIR-177
> URL: http://jira.codehaus.org/browse/MPIR-177
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Improvement
> Affects Versions: 2.1
> Reporter: Michael Hinterseher
> Priority: Minor
>
> 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...
--
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
[jira] Moved: (MPIR-177) Generation of HTML dependency report takes
a long time due to accessing repositories not specified in pom
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPIR-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann moved MDEP-189 to MPIR-177:
---------------------------------------------
Affects Version/s: (was: 2.0)
2.1
Key: MPIR-177 (was: MDEP-189)
Project: Maven 2.x Project Info Reports Plugin (was: Maven 2.x Dependency Plugin)
> Generation of HTML dependency report takes a long time due to accessing repositories not specified in pom
> ---------------------------------------------------------------------------------------------------------
>
> Key: MPIR-177
> URL: http://jira.codehaus.org/browse/MPIR-177
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Improvement
> Affects Versions: 2.1
> Reporter: Michael Hinterseher
> Assignee: Brian Fox
> Priority: Minor
>
> 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...
--
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
[jira] Commented: (MDEP-189) Generation of HTML dependency report
takes a long time due to accessing repositories not specified in pom
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154760#action_154760 ]
Brian Fox commented on MDEP-189:
--------------------------------
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.
> Generation of HTML dependency report takes a long time due to accessing repositories not specified in pom
> ---------------------------------------------------------------------------------------------------------
>
> Key: MDEP-189
> URL: http://jira.codehaus.org/browse/MDEP-189
> Project: Maven 2.x Dependency Plugin
> Issue Type: Improvement
> Affects Versions: 2.0
> Reporter: Michael Hinterseher
> Assignee: Brian Fox
> Priority: Minor
>
> 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...
--
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
[jira] Commented: (MDEP-189) Generation of HTML dependency report
takes a long time due to accessing repositories not specified in pom
Posted by "EJ Ciramella (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197284#action_197284 ]
EJ Ciramella commented on MDEP-189:
-----------------------------------
What's the easiest way to detect this?
Some dependencies have a slew of dependencies as well.
> Generation of HTML dependency report takes a long time due to accessing repositories not specified in pom
> ---------------------------------------------------------------------------------------------------------
>
> Key: MDEP-189
> URL: http://jira.codehaus.org/browse/MDEP-189
> Project: Maven 2.x Dependency Plugin
> Issue Type: Improvement
> Affects Versions: 2.0
> Reporter: Michael Hinterseher
> Assignee: Brian Fox
> Priority: Minor
>
> 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...
--
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
[jira] Commented: (MPIR-177) Generation of HTML dependency report
takes a long time due to accessing repositories not specified in pom
Posted by "EJ Ciramella (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPIR-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197361#action_197361 ]
EJ Ciramella commented on MPIR-177:
-----------------------------------
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.
> Generation of HTML dependency report takes a long time due to accessing repositories not specified in pom
> ---------------------------------------------------------------------------------------------------------
>
> Key: MPIR-177
> URL: http://jira.codehaus.org/browse/MPIR-177
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Improvement
> Affects Versions: 2.1
> Reporter: Michael Hinterseher
> Priority: Minor
>
> 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...
--
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
[jira] Closed: (MPIR-177) Generation of HTML dependency report
takes a long time due to accessing repositories not specified in pom
Posted by "Michael Hinterseher (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPIR-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Hinterseher closed MPIR-177.
------------------------------------
Resolution: Duplicate
Fix Version/s: 2.2
> Generation of HTML dependency report takes a long time due to accessing repositories not specified in pom
> ---------------------------------------------------------------------------------------------------------
>
> Key: MPIR-177
> URL: http://jira.codehaus.org/browse/MPIR-177
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Improvement
> Affects Versions: 2.1
> Reporter: Michael Hinterseher
> Priority: Minor
> Fix For: 2.2
>
>
> 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...
--
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