For each dependencies, URL are checked to retrieve data.
To disable use this tip :
<reporting>
        <plugins>
                <plugin>
                        <groupId>org.apache.maven.plugins</groupId>
                        
<artifactId>maven-project-info-reports-plugin</artifactId>
                        <configuration>
                                
<dependencyLocationsEnabled>false</dependencyLocationsEnabled>
                                <offline>true</offline>
                        </configuration>
                </plugin>
        </plugins>
</reporting>

Also, some data would not present in the dependencies report.

Fabrice

On Tue, Aug 4, 2009 at 8:49 PM, Andrew Goktepe<andrewgokt...@gmail.com> wrote:
> I did encounter the same problem.  The build does eventually proceed, but
> after several minutes per module.  In our multi-module build this more than
> doubles the release build time.
>
> Setting dependencyLocationsEnabled to false speeds this up:
> http://maven.apache.org/plugins/maven-project-info-reports-plugin/dependencies-mojo.html
>
> You might also try dependencyDetailsEnabled=false.  I haven't tried that one
> yet.
>
> -Andrew
>
> On Mon, Aug 3, 2009 at 6:26 AM, Jörg Schaible <joerg.schai...@gmx.de> wrote:
>
>> Hi guys,
>>
>> did anyone of you encounter the problem, that the release-plugin freezes in
>> preparation performing the dependency check for the snapshots? The project
>> itself builds a plugin:
>>
>> ============== %< ================
>> $ mvn org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:prepare
>> [INFO] Scanning for projects...
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Building Scalaris QMB Plugin
>> [INFO]    task-segment:
>> [org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:prepare]
>> (aggregator-style)
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] [release:prepare {execution: default-cli}]
>> [INFO] Verifying that there are no local modifications...
>> [INFO] Executing: /bin/sh -c cd /home/jos/work/plugins/qmb-plugin &&
>> svn --non-interactive status
>> [INFO] Working directory: /home/jos/work/plugins/qmb-plugin
>> [INFO] Checking dependencies and plugins for snapshots ...
>> ============== %< ================
>>
>> .. and that's it. All I can do is killing the process (after several
>> minutes). It does not seem a regression though. I tried with M221-rc1,
>> M220, M210, M2010 and M209 in combination with release plugin version
>> 2.0-beta-9 and 2.0-beta-8. Also it does not give a lot of more log entries
>> after invoking the release:prepare goal using -X as start option.
>>
>> I can create the dependency-report as well as calling dependency:tree
>> though.
>>
>> What might cause this? Since I am sure that I do not trigger any snapshot,
>> can I omit the dependency check somehow?
>>
>> - Jörg
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Reply via email to