-
-
Notifications
You must be signed in to change notification settings - Fork 6
Expand file tree
/
Copy pathsettings.xml
More file actions
92 lines (81 loc) · 3.7 KB
/
Copy pathsettings.xml
File metadata and controls
92 lines (81 loc) · 3.7 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
<settings>
<mirrors>
<mirror>
<id>nexus</id>
<mirrorOf>*</mirrorOf>
<url>https://build-repo.stackable.tech/repository/maven-public/</url>
</mirror>
</mirrors>
<profiles>
<profile>
<id>stackable</id>
<!--Enable snapshots for the built-in central repo to direct -->
<!--all requests to nexus via the mirror -->
<repositories>
<repository>
<id>central</id>
<url>http://central</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>central</id>
<url>http://central</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</pluginRepository>
</pluginRepositories>
<properties>
<!--
Resolver specific configuration keys can be found here: https://maven.apache.org/resolver/configuration.html
This is to work around an issue where Maven builds in Github Actions would randomly fail.
There is some evidence that points at Azure networking as the root cause where it closes idle connections (silently) after 4 minutes.
Maven would then sometimes reuse an "old" connection from its connection pool and would encounter issues due to these connection closures.
This patch changes the TTL for the connections to a lower value than 4 minutes (240s), the default is 300s (5min).
There are two properties here because sometimes in November 2023 the name was changed.
The new name will only take effect as of Maven 4, but it doesn't hurt to add it here already, therefore, we just add both properties here.
https://issues.apache.org/jira/browse/MRESOLVER-440
-->
<!-- Old name: maven-resolver 1.x, Maven 3.x -->
<aether.connector.http.connectionMaxTtl>25</aether.connector.http.connectionMaxTtl>
<!-- New name: maven-resolver 2.x, as of Maven 4.x -->
<aether.transport.http.connectionMaxTtl>25</aether.transport.http.connectionMaxTtl>
<!--
By default, requests are retried 3 times. We increase the count slightly to hopefully get less failing
builds in CI.
-->
<aether.transport.http.retryHandler.count>5</aether.transport.http.retryHandler.count>
<!--
By default, retries wait for 5000 milliseconds (5 seconds). We increase this to 10000 milliseconds
(10 seconds) to spam the Nexus instance a little less.
-->
<aether.transport.http.retryHandler.interval>10000</aether.transport.http.retryHandler.interval>
<!--
Servers can respond with `Retry-After` headers. By default, the value is capped at 300000 milliseconds (300
seconds). We reduce this to 60000 (60 seconds) to avoid super long retry intervals.
-->
<aether.transport.http.retryHandler.intervalMax>60000</aether.transport.http.retryHandler.intervalMax>
<!--
This is an option we can experiment with in the future. Settings this to false will result in no connection
pooling, which should help to avoid stale/long-lasting connections which can become inactive and be killed by
the Azure networking.
-->
<!-- <aether.transport.http.reuseConnections>false</aether.transport.http.reuseConnections> -->
</properties>
</profile>
</profiles>
<activeProfiles>
<!--make the stackable profile active all the time -->
<activeProfile>stackable</activeProfile>
</activeProfiles>
</settings>