[ 
https://issues.apache.org/jira/browse/MNGSITE-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17715440#comment-17715440
 ] 

ASF GitHub Bot commented on MNGSITE-393:
----------------------------------------

elharo commented on code in PR #212:
URL: https://github.com/apache/maven-site/pull/212#discussion_r1174557289


##########
content/apt/guides/mini/guide-http-settings.apt:
##########
@@ -33,28 +33,28 @@ Advanced Configuration of the HttpClient HTTP Wagon
   You can use the default wagon implementation for a given
   protocol, or you can select an alternative wagon <<<provider>>> on a 
per-protocol basis. 
   For more information, see the {{{./guide-wagon-providers.html}Guide to Wagon 
Providers}} \[3\].
-  The default wagon http(s) is the HttpClient based on 
{{{http://hc.apache.org/httpcomponents-client-ga}Apache Http Client 4.1.2}}.
-  HTTP connection pooling prevents reopening http(s) to remote server for each 
requests.
+  The default wagon http(s) is the HttpClient based on 
{{{https://hc.apache.org/httpcomponents-client-4.5.x/}Apache Http Client 4.5}}.
+  HTTP connection pooling prevents reopening new connections to the same 
server for each request.
   This pool feature is configurable with some parameters \[4\].
   The default wagon comes with some default configuration:
 
   * http(s) connection pool: default to 20.
 
-  * readTimeout: default to 1800000ms (~30 minutes) (see section <<<Read time 
out>>> below)
+  * readTimeout: default to 1,800,000ms (~30 minutes) (see section <<<Read 
time out>>> below)

Review Comment:
   reverted 1800000 since it's a Java property and this is the Java default 
value





> Remove references to Maven 2.x
> ------------------------------
>
>                 Key: MNGSITE-393
>                 URL: https://issues.apache.org/jira/browse/MNGSITE-393
>             Project: Maven Project Web Site
>          Issue Type: Improvement
>            Reporter: Elliotte Rusty Harold
>            Assignee: Elliotte Rusty Harold
>            Priority: Major
>          Time Spent: 4h
>  Remaining Estimate: 0h
>
> Maven 3.x is over a decade old now and we're talking about Maven 4. It's time 
> to clean out all the random discussion here and there about how Maven 2.x did 
> things, differences between Maven 2 and 3, what works in Maven 3 but not 2, 
> etc. 
> Assume Maven 3.0 as the minimum, probably Maven 3.1.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to