Linux中Maven的下载与配置

1
2
3
4
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

      xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">

1
2
3
4
5
6
7
8
<!-- pluginGroup

 | Specifies a further group identifier to use for plugin lookup.

<pluginGroup>com.your.plugins</pluginGroup>

-->

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
<!-- proxy

 | Specification for one proxy, to be used in connecting to the network.

 |

<proxy>

  <id>optional</id>

  <active>true</active>

  <protocol>http</protocol>

  <username>proxyuser</username>

  <password>proxypass</password>

  <host>proxy.host.net</host>

  <port>80</port>

  <nonProxyHosts>local.net|some.host.com</nonProxyHosts>

</proxy>

-->

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
<!-- server

 | Specifies the authentication information to use when connecting to a particular server, identified by

 | a unique name within the system (referred to by the 'id' attribute below).

 |

 | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are

 |       used together.

 |

<server>

  <id>deploymentRepo</id>

  <username>repouser</username>

  <password>repopwd</password>

</server>

-->



<!-- Another sample, using keys to authenticate.

<server>

  <id>siteServer</id>

  <privateKey>/path/to/private/key</privateKey>

  <passphrase>optional; leave empty if not used.</passphrase>

</server>

-->

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
<!-- mirror

 | Specifies a repository mirror site to use instead of a given repository. The repository that

 | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used

 | for inheritance and direct lookup purposes, and must be unique across the set of mirrors.

 |

<mirror>

  <id>mirrorId</id>

  <mirrorOf>repositoryId</mirrorOf>

  <name>Human Readable Name for this Mirror.</name>

  <url>http://my.repository.com/repo/path</url>

</mirror>

 -->

<!-- 阿里云仓库 -->

    <mirror>

        <id>alimaven</id>

        <mirrorOf>central</mirrorOf>

        <name>aliyun maven</name>

        <url>http://maven.aliyun.com/nexus/content/repositories/central/</url>

    </mirror>

	



	<!-- 中央仓库1 -->

    <mirror>

        <id>repo1</id>

        <mirrorOf>central</mirrorOf>

        <name>Human Readable Name for this Mirror.</name>

        <url>http://repo1.maven.org/maven2/</url>

    </mirror>

 

    <!-- 中央仓库2 -->

    <mirror>

        <id>repo2</id>

        <mirrorOf>central</mirrorOf>

        <name>Human Readable Name for this Mirror.</name>

        <url>http://repo2.maven.org/maven2/</url>

    </mirror>

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
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
<!-- profile

 | Specifies a set of introductions to the build process, to be activated using one or more of the

 | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>

 | or the command line, profiles have to have an ID that is unique.

 |

 | An encouraged best practice for profile identification is to use a consistent naming convention

 | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.

 | This will make it more intuitive to understand what the set of introduced profiles is attempting

 | to accomplish, particularly when you only have a list of profile id's for debug.

 |

 | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.

<profile>

  <id>jdk-1.4</id>



  <activation>

    <jdk>1.4</jdk>

  </activation>



  <repositories>

    <repository>

      <id>jdk15</id>

      <name>Repository for JDK 1.4 builds</name>

      <url>http://www.myhost.com/maven/jdk15</url>

      <layout>default</layout>

      <snapshotPolicy>always</snapshotPolicy>

    </repository>

  </repositories>

</profile>

-->



<!--

 | Here is another profile, activated by the system property 'target-env' with a value of 'dev',

 | which provides a specific path to the Tomcat instance. To use this, your plugin configuration

 | might hypothetically look like:

 |

 | ...

 | <plugin>

 |   <groupId>org.myco.myplugins</groupId>

 |   <artifactId>myplugin</artifactId>

 |

 |   <configuration>

 |     <tomcatLocation>${tomcatPath}</tomcatLocation>

 |   </configuration>

 | </plugin>

 | ...

 |

 | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to

 |       anything, you could just leave off the <value/> inside the activation-property.

 |

<profile>

  <id>env-dev</id>



  <activation>

    <property>

      <name>target-env</name>

      <value>dev</value>

    </property>

  </activation>



  <properties>

    <tomcatPath>/path/to/tomcat/instance</tomcatPath>

  </properties>

</profile>

-->

<profile>     

  <id>jdk</id>   

  <activation>        

        <activeByDefault>true</activeByDefault>    

        <jdk>17</jdk>      

  </activation>  

  <properties>  

	<maven.compiler.source>17</maven.compiler.source> 

	<maven.compiler.target>17</maven.compiler.target> 

	<maven.compiler.compilerVersion>17</maven.compiler.compilerVersion>   

	<maven.compiler.encoding>utf-8</maven.compiler.encoding>

	<project.build.sourceEncoding>utf-8</project.build.sourceEncoding>

	<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>

	<maven.test.failure.ignore>true</maven.test.failure.ignore>

	<maven.test.skip>true</maven.test.skip>

  </properties>

</profile>