|
@@ -46,297 +46,297 @@ under the License.
|
46
|
46
|
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
|
47
|
47
|
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
|
48
|
48
|
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
|
49
|
|
- <!-- localRepository
|
50
|
|
- | The path to the local repository maven will use to store artifacts.
|
51
|
|
- |
|
52
|
|
- | Default: ${user.home}/.m2/repository
|
53
|
|
- <localRepository>/path/to/local/repo</localRepository>
|
54
|
|
- -->
|
55
|
|
- <localRepository>D:/repository</localRepository>
|
56
|
|
-
|
57
|
|
- <!-- interactiveMode
|
58
|
|
- | This will determine whether maven prompts you when it needs input. If set to false,
|
59
|
|
- | maven will use a sensible default value, perhaps based on some other setting, for
|
60
|
|
- | the parameter in question.
|
61
|
|
- |
|
62
|
|
- | Default: true
|
63
|
|
- <interactiveMode>true</interactiveMode>
|
64
|
|
- -->
|
65
|
|
-
|
66
|
|
- <!-- offline
|
67
|
|
- | Determines whether maven should attempt to connect to the network when executing a build.
|
68
|
|
- | This will have an effect on artifact downloads, artifact deployment, and others.
|
69
|
|
- |
|
70
|
|
- | Default: false
|
71
|
|
- <offline>false</offline>
|
72
|
|
- -->
|
73
|
|
-
|
74
|
|
- <!-- pluginGroups
|
75
|
|
- | This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.
|
76
|
|
- | when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers
|
77
|
|
- | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.
|
78
|
|
- |-->
|
79
|
|
- <pluginGroups>
|
80
|
|
- <!-- pluginGroup
|
81
|
|
- | Specifies a further group identifier to use for plugin lookup.
|
82
|
|
- <pluginGroup>com.your.plugins</pluginGroup>
|
|
49
|
+ <!-- localRepository
|
|
50
|
+ | The path to the local repository maven will use to store artifacts.
|
|
51
|
+ |
|
|
52
|
+ | Default: ${user.home}/.m2/repository
|
|
53
|
+ <localRepository>/path/to/local/repo</localRepository>
|
83
|
54
|
-->
|
84
|
|
- </pluginGroups>
|
|
55
|
+ <localRepository>D:/repository</localRepository>
|
85
|
56
|
|
86
|
|
- <!-- proxies
|
87
|
|
- | This is a list of proxies which can be used on this machine to connect to the network.
|
88
|
|
- | Unless otherwise specified (by system property or command-line switch), the first proxy
|
89
|
|
- | specification in this list marked as active will be used.
|
90
|
|
- |-->
|
91
|
|
- <proxies>
|
92
|
|
- <!-- proxy
|
93
|
|
- | Specification for one proxy, to be used in connecting to the network.
|
|
57
|
+ <!-- interactiveMode
|
|
58
|
+ | This will determine whether maven prompts you when it needs input. If set to false,
|
|
59
|
+ | maven will use a sensible default value, perhaps based on some other setting, for
|
|
60
|
+ | the parameter in question.
|
94
|
61
|
|
|
95
|
|
- <proxy>
|
96
|
|
- <id>optional</id>
|
97
|
|
- <active>true</active>
|
98
|
|
- <protocol>http</protocol>
|
99
|
|
- <username>proxyuser</username>
|
100
|
|
- <password>proxypass</password>
|
101
|
|
- <host>proxy.host.net</host>
|
102
|
|
- <port>80</port>
|
103
|
|
- <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
|
104
|
|
- </proxy>
|
|
62
|
+ | Default: true
|
|
63
|
+ <interactiveMode>true</interactiveMode>
|
105
|
64
|
-->
|
106
|
|
- </proxies>
|
107
|
65
|
|
108
|
|
- <!-- servers
|
109
|
|
- | This is a list of authentication profiles, keyed by the server-id used within the system.
|
110
|
|
- | Authentication profiles can be used whenever maven must make a connection to a remote server.
|
111
|
|
- |-->
|
112
|
|
- <servers>
|
113
|
|
- <!-- server
|
114
|
|
- | Specifies the authentication information to use when connecting to a particular server, identified by
|
115
|
|
- | a unique name within the system (referred to by the 'id' attribute below).
|
116
|
|
- |
|
117
|
|
- | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are
|
118
|
|
- | used together.
|
|
66
|
+ <!-- offline
|
|
67
|
+ | Determines whether maven should attempt to connect to the network when executing a build.
|
|
68
|
+ | This will have an effect on artifact downloads, artifact deployment, and others.
|
119
|
69
|
|
|
120
|
|
- <server>
|
121
|
|
- <id>deploymentRepo</id>
|
122
|
|
- <username>repouser</username>
|
123
|
|
- <password>repopwd</password>
|
124
|
|
- </server>
|
|
70
|
+ | Default: false
|
|
71
|
+ <offline>false</offline>
|
125
|
72
|
-->
|
126
|
73
|
|
127
|
|
- <!-- Another sample, using keys to authenticate.
|
128
|
|
- <server>
|
129
|
|
- <id>siteServer</id>
|
130
|
|
- <privateKey>/path/to/private/key</privateKey>
|
131
|
|
- <passphrase>optional; leave empty if not used.</passphrase>
|
132
|
|
- </server>
|
133
|
|
- -->
|
134
|
|
- <server>
|
135
|
|
- <id>releases</id>
|
136
|
|
- <username>admin</username>
|
137
|
|
- <password>123456</password>
|
138
|
|
- </server>
|
139
|
|
- <server>
|
140
|
|
- <id>snapshots</id>
|
141
|
|
- <username>admin</username>
|
142
|
|
- <password>123456</password>
|
143
|
|
- </server>
|
144
|
|
- </servers>
|
|
74
|
+ <!-- pluginGroups
|
|
75
|
+ | This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.
|
|
76
|
+ | when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers
|
|
77
|
+ | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.
|
|
78
|
+ |-->
|
|
79
|
+ <pluginGroups>
|
|
80
|
+ <!-- pluginGroup
|
|
81
|
+ | Specifies a further group identifier to use for plugin lookup.
|
|
82
|
+ <pluginGroup>com.your.plugins</pluginGroup>
|
|
83
|
+ -->
|
|
84
|
+ </pluginGroups>
|
145
|
85
|
|
146
|
|
- <!-- mirrors
|
147
|
|
- | This is a list of mirrors to be used in downloading artifacts from remote repositories.
|
148
|
|
- |
|
149
|
|
- | It works like this: a POM may declare a repository to use in resolving certain artifacts.
|
150
|
|
- | However, this repository may have problems with heavy traffic at times, so people have mirrored
|
151
|
|
- | it to several places.
|
152
|
|
- |
|
153
|
|
- | That repository definition will have a unique id, so we can create a mirror reference for that
|
154
|
|
- | repository, to be used as an alternate download site. The mirror site will be the preferred
|
155
|
|
- | server for that repository.
|
156
|
|
- |-->
|
157
|
|
- <mirrors>
|
158
|
|
- <!-- mirror
|
159
|
|
- | Specifies a repository mirror site to use instead of a given repository. The repository that
|
160
|
|
- | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
|
161
|
|
- | for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
|
162
|
|
- |
|
163
|
|
- <mirror>
|
164
|
|
- <id>mirrorId</id>
|
165
|
|
- <mirrorOf>repositoryId</mirrorOf>
|
166
|
|
- <name>Human Readable Name for this Mirror.</name>
|
167
|
|
- <url>http://my.repository.com/repo/path</url>
|
168
|
|
- </mirror>
|
169
|
|
-
|
170
|
|
- <mirror>
|
171
|
|
- <id>aliyunmaven</id>
|
172
|
|
- <mirrorOf>*</mirrorOf>
|
173
|
|
- <name>阿里云公共仓库</name>
|
174
|
|
- <url>https://maven.aliyun.com/repository/public</url>
|
175
|
|
- </mirror>
|
176
|
|
-
|
177
|
|
- -->
|
178
|
|
- <mirror>
|
179
|
|
- <id>nexus</id>
|
180
|
|
- <name>maven-public</name>
|
181
|
|
- <url>http://117.34.118.57:28081/repository/maven-public/</url>
|
182
|
|
- <mirrorOf>*</mirrorOf>
|
183
|
|
- </mirror>
|
184
|
|
-
|
185
|
|
- </mirrors>
|
|
86
|
+ <!-- proxies
|
|
87
|
+ | This is a list of proxies which can be used on this machine to connect to the network.
|
|
88
|
+ | Unless otherwise specified (by system property or command-line switch), the first proxy
|
|
89
|
+ | specification in this list marked as active will be used.
|
|
90
|
+ |-->
|
|
91
|
+ <proxies>
|
|
92
|
+ <!-- proxy
|
|
93
|
+ | Specification for one proxy, to be used in connecting to the network.
|
|
94
|
+ |
|
|
95
|
+ <proxy>
|
|
96
|
+ <id>optional</id>
|
|
97
|
+ <active>true</active>
|
|
98
|
+ <protocol>http</protocol>
|
|
99
|
+ <username>proxyuser</username>
|
|
100
|
+ <password>proxypass</password>
|
|
101
|
+ <host>proxy.host.net</host>
|
|
102
|
+ <port>80</port>
|
|
103
|
+ <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
|
|
104
|
+ </proxy>
|
|
105
|
+ -->
|
|
106
|
+ </proxies>
|
|
107
|
+
|
|
108
|
+ <!-- servers
|
|
109
|
+ | This is a list of authentication profiles, keyed by the server-id used within the system.
|
|
110
|
+ | Authentication profiles can be used whenever maven must make a connection to a remote server.
|
|
111
|
+ |-->
|
|
112
|
+ <servers>
|
|
113
|
+ <!-- server
|
|
114
|
+ | Specifies the authentication information to use when connecting to a particular server, identified by
|
|
115
|
+ | a unique name within the system (referred to by the 'id' attribute below).
|
|
116
|
+ |
|
|
117
|
+ | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are
|
|
118
|
+ | used together.
|
|
119
|
+ |
|
|
120
|
+ <server>
|
|
121
|
+ <id>deploymentRepo</id>
|
|
122
|
+ <username>repouser</username>
|
|
123
|
+ <password>repopwd</password>
|
|
124
|
+ </server>
|
|
125
|
+ -->
|
|
126
|
+
|
|
127
|
+ <!-- Another sample, using keys to authenticate.
|
|
128
|
+ <server>
|
|
129
|
+ <id>siteServer</id>
|
|
130
|
+ <privateKey>/path/to/private/key</privateKey>
|
|
131
|
+ <passphrase>optional; leave empty if not used.</passphrase>
|
|
132
|
+ </server>
|
|
133
|
+ -->
|
|
134
|
+ <server>
|
|
135
|
+ <id>releases</id>
|
|
136
|
+ <username>admin</username>
|
|
137
|
+ <password>123456</password>
|
|
138
|
+ </server>
|
|
139
|
+ <server>
|
|
140
|
+ <id>snapshots</id>
|
|
141
|
+ <username>admin</username>
|
|
142
|
+ <password>123456</password>
|
|
143
|
+ </server>
|
|
144
|
+ </servers>
|
186
|
145
|
|
187
|
|
- <!-- profiles
|
188
|
|
- | This is a list of profiles which can be activated in a variety of ways, and which can modify
|
189
|
|
- | the build process. Profiles provided in the settings.xml are intended to provide local machine-
|
190
|
|
- | specific paths and repository locations which allow the build to work in the local environment.
|
191
|
|
- |
|
192
|
|
- | For example, if you have an integration testing plugin - like cactus - that needs to know where
|
193
|
|
- | your Tomcat instance is installed, you can provide a variable here such that the variable is
|
194
|
|
- | dereferenced during the build process to configure the cactus plugin.
|
195
|
|
- |
|
196
|
|
- | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
|
197
|
|
- | section of this document (settings.xml) - will be discussed later. Another way essentially
|
198
|
|
- | relies on the detection of a system property, either matching a particular value for the property,
|
199
|
|
- | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
|
200
|
|
- | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
|
201
|
|
- | Finally, the list of active profiles can be specified directly from the command line.
|
202
|
|
- |
|
203
|
|
- | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
|
204
|
|
- | repositories, plugin repositories, and free-form properties to be used as configuration
|
205
|
|
- | variables for plugins in the POM.
|
206
|
|
- |
|
207
|
|
- |-->
|
208
|
|
- <profiles>
|
209
|
|
- <!-- profile
|
210
|
|
- | Specifies a set of introductions to the build process, to be activated using one or more of the
|
211
|
|
- | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
|
212
|
|
- | or the command line, profiles have to have an ID that is unique.
|
|
146
|
+ <!-- mirrors
|
|
147
|
+ | This is a list of mirrors to be used in downloading artifacts from remote repositories.
|
213
|
148
|
|
|
214
|
|
- | An encouraged best practice for profile identification is to use a consistent naming convention
|
215
|
|
- | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
|
216
|
|
- | This will make it more intuitive to understand what the set of introduced profiles is attempting
|
217
|
|
- | to accomplish, particularly when you only have a list of profile id's for debug.
|
|
149
|
+ | It works like this: a POM may declare a repository to use in resolving certain artifacts.
|
|
150
|
+ | However, this repository may have problems with heavy traffic at times, so people have mirrored
|
|
151
|
+ | it to several places.
|
218
|
152
|
|
|
219
|
|
- | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
|
220
|
|
- <profile>
|
221
|
|
- <id>jdk-1.4</id>
|
|
153
|
+ | That repository definition will have a unique id, so we can create a mirror reference for that
|
|
154
|
+ | repository, to be used as an alternate download site. The mirror site will be the preferred
|
|
155
|
+ | server for that repository.
|
|
156
|
+ |-->
|
|
157
|
+ <mirrors>
|
|
158
|
+ <!-- mirror
|
|
159
|
+ | Specifies a repository mirror site to use instead of a given repository. The repository that
|
|
160
|
+ | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
|
|
161
|
+ | for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
|
|
162
|
+ |
|
|
163
|
+ <mirror>
|
|
164
|
+ <id>mirrorId</id>
|
|
165
|
+ <mirrorOf>repositoryId</mirrorOf>
|
|
166
|
+ <name>Human Readable Name for this Mirror.</name>
|
|
167
|
+ <url>http://my.repository.com/repo/path</url>
|
|
168
|
+ </mirror>
|
222
|
169
|
|
223
|
|
- <activation>
|
224
|
|
- <jdk>1.4</jdk>
|
225
|
|
- </activation>
|
|
170
|
+ <mirror>
|
|
171
|
+ <id>aliyunmaven</id>
|
|
172
|
+ <mirrorOf>*</mirrorOf>
|
|
173
|
+ <name>阿里云公共仓库</name>
|
|
174
|
+ <url>https://maven.aliyun.com/repository/public</url>
|
|
175
|
+ </mirror>
|
226
|
176
|
|
227
|
|
- <repositories>
|
228
|
|
- <repository>
|
229
|
|
- <id>jdk14</id>
|
230
|
|
- <name>Repository for JDK 1.4 builds</name>
|
231
|
|
- <url>http://www.myhost.com/maven/jdk14</url>
|
232
|
|
- <layout>default</layout>
|
233
|
|
- <snapshotPolicy>always</snapshotPolicy>
|
234
|
|
- </repository>
|
235
|
|
- </repositories>
|
236
|
|
- </profile>
|
237
|
|
- -->
|
238
|
|
-<profile>
|
239
|
|
- <activation>
|
240
|
|
- <!-- 默认激活此 profile -->
|
241
|
|
- <activeByDefault>true</activeByDefault>
|
242
|
|
- </activation>
|
243
|
|
- <repositories>
|
244
|
|
- <repository>
|
245
|
|
- <id>nexus</id>
|
246
|
|
- <name>Nexus Repository</name>
|
247
|
|
- <url>http://117.34.118.57:28081/repository/maven-public/</url>
|
248
|
|
- <releases>
|
249
|
|
- <enabled>true</enabled>
|
250
|
|
- </releases>
|
251
|
|
- </repository>
|
252
|
|
-
|
253
|
|
- <repository>
|
254
|
|
- <id>central</id>
|
255
|
|
- <name>Nexus Central Repository</name>
|
256
|
|
- <url>http://117.34.118.57:28081/repository/maven-central/</url>
|
257
|
|
- <releases>
|
258
|
|
- <enabled>true</enabled>
|
259
|
|
- </releases>
|
260
|
|
- <snapshots>
|
261
|
|
- <enabled>false</enabled>
|
262
|
|
- </snapshots>
|
263
|
|
- </repository>
|
264
|
|
-
|
265
|
|
- <repository>
|
266
|
|
- <id>release</id>
|
267
|
|
- <name>Nexus Release Repository</name>
|
268
|
|
- <url>http://117.34.118.57:28081/repository/maven-releases/</url>
|
269
|
|
- <releases>
|
270
|
|
- <enabled>true</enabled>
|
271
|
|
- </releases>
|
272
|
|
- <snapshots>
|
273
|
|
- <enabled>false</enabled>
|
274
|
|
- </snapshots>
|
275
|
|
- </repository>
|
276
|
|
-
|
277
|
|
- <repository>
|
278
|
|
- <id>snapshots</id>
|
279
|
|
- <name>Nexus Snapshots Repository</name>
|
280
|
|
- <url>http://117.34.118.57:28081/repository/maven-snapshots/</url>
|
281
|
|
- <releases>
|
282
|
|
- <enabled>true</enabled>
|
283
|
|
- </releases>
|
284
|
|
- <snapshots>
|
285
|
|
- <enabled>true</enabled>
|
286
|
|
- </snapshots>
|
287
|
|
- </repository>
|
288
|
|
- </repositories>
|
289
|
|
-
|
290
|
|
- <pluginRepositories>
|
291
|
|
- <pluginRepository>
|
292
|
|
- <id>plugins</id>
|
293
|
|
- <name>Nexus Plugin Repositories</name>
|
294
|
|
- <url>http://117.34.118.57:28081/repository/maven-public/</url>
|
295
|
|
- </pluginRepository>
|
296
|
|
- </pluginRepositories>
|
297
|
|
- </profile>
|
298
|
|
- <!--
|
299
|
|
- | Here is another profile, activated by the system property 'target-env' with a value of 'dev',
|
300
|
|
- | which provides a specific path to the Tomcat instance. To use this, your plugin configuration
|
301
|
|
- | might hypothetically look like:
|
|
177
|
+ -->
|
|
178
|
+ <mirror>
|
|
179
|
+ <id>nexus</id>
|
|
180
|
+ <name>maven-public</name>
|
|
181
|
+ <url>http://117.34.118.57:28081/repository/maven-public/</url>
|
|
182
|
+ <mirrorOf>*</mirrorOf>
|
|
183
|
+ </mirror>
|
|
184
|
+
|
|
185
|
+ </mirrors>
|
|
186
|
+
|
|
187
|
+ <!-- profiles
|
|
188
|
+ | This is a list of profiles which can be activated in a variety of ways, and which can modify
|
|
189
|
+ | the build process. Profiles provided in the settings.xml are intended to provide local machine-
|
|
190
|
+ | specific paths and repository locations which allow the build to work in the local environment.
|
302
|
191
|
|
|
303
|
|
- | ...
|
304
|
|
- | <plugin>
|
305
|
|
- | <groupId>org.myco.myplugins</groupId>
|
306
|
|
- | <artifactId>myplugin</artifactId>
|
|
192
|
+ | For example, if you have an integration testing plugin - like cactus - that needs to know where
|
|
193
|
+ | your Tomcat instance is installed, you can provide a variable here such that the variable is
|
|
194
|
+ | dereferenced during the build process to configure the cactus plugin.
|
307
|
195
|
|
|
308
|
|
- | <configuration>
|
309
|
|
- | <tomcatLocation>${tomcatPath}</tomcatLocation>
|
310
|
|
- | </configuration>
|
311
|
|
- | </plugin>
|
312
|
|
- | ...
|
|
196
|
+ | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
|
|
197
|
+ | section of this document (settings.xml) - will be discussed later. Another way essentially
|
|
198
|
+ | relies on the detection of a system property, either matching a particular value for the property,
|
|
199
|
+ | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
|
|
200
|
+ | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
|
|
201
|
+ | Finally, the list of active profiles can be specified directly from the command line.
|
313
|
202
|
|
|
314
|
|
- | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
|
315
|
|
- | anything, you could just leave off the <value/> inside the activation-property.
|
|
203
|
+ | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
|
|
204
|
+ | repositories, plugin repositories, and free-form properties to be used as configuration
|
|
205
|
+ | variables for plugins in the POM.
|
316
|
206
|
|
|
317
|
|
- <profile>
|
318
|
|
- <id>env-dev</id>
|
|
207
|
+ |-->
|
|
208
|
+ <profiles>
|
|
209
|
+ <!-- profile
|
|
210
|
+ | Specifies a set of introductions to the build process, to be activated using one or more of the
|
|
211
|
+ | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
|
|
212
|
+ | or the command line, profiles have to have an ID that is unique.
|
|
213
|
+ |
|
|
214
|
+ | An encouraged best practice for profile identification is to use a consistent naming convention
|
|
215
|
+ | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
|
|
216
|
+ | This will make it more intuitive to understand what the set of introduced profiles is attempting
|
|
217
|
+ | to accomplish, particularly when you only have a list of profile id's for debug.
|
|
218
|
+ |
|
|
219
|
+ | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
|
|
220
|
+ <profile>
|
|
221
|
+ <id>jdk-1.4</id>
|
319
|
222
|
|
320
|
|
- <activation>
|
321
|
|
- <property>
|
322
|
|
- <name>target-env</name>
|
323
|
|
- <value>dev</value>
|
324
|
|
- </property>
|
325
|
|
- </activation>
|
|
223
|
+ <activation>
|
|
224
|
+ <jdk>1.4</jdk>
|
|
225
|
+ </activation>
|
326
|
226
|
|
327
|
|
- <properties>
|
328
|
|
- <tomcatPath>/path/to/tomcat/instance</tomcatPath>
|
329
|
|
- </properties>
|
330
|
|
- </profile>
|
331
|
|
- -->
|
332
|
|
- </profiles>
|
|
227
|
+ <repositories>
|
|
228
|
+ <repository>
|
|
229
|
+ <id>jdk14</id>
|
|
230
|
+ <name>Repository for JDK 1.4 builds</name>
|
|
231
|
+ <url>http://www.myhost.com/maven/jdk14</url>
|
|
232
|
+ <layout>default</layout>
|
|
233
|
+ <snapshotPolicy>always</snapshotPolicy>
|
|
234
|
+ </repository>
|
|
235
|
+ </repositories>
|
|
236
|
+ </profile>
|
|
237
|
+ -->
|
|
238
|
+ <profile>
|
|
239
|
+ <activation>
|
|
240
|
+ <!-- 默认激活此 profile -->
|
|
241
|
+ <activeByDefault>true</activeByDefault>
|
|
242
|
+ </activation>
|
|
243
|
+ <repositories>
|
|
244
|
+ <repository>
|
|
245
|
+ <id>nexus</id>
|
|
246
|
+ <name>Nexus Repository</name>
|
|
247
|
+ <url>http://117.34.118.57:28081/repository/maven-public/</url>
|
|
248
|
+ <releases>
|
|
249
|
+ <enabled>true</enabled>
|
|
250
|
+ </releases>
|
|
251
|
+ </repository>
|
|
252
|
+
|
|
253
|
+ <repository>
|
|
254
|
+ <id>central</id>
|
|
255
|
+ <name>Nexus Central Repository</name>
|
|
256
|
+ <url>http://117.34.118.57:28081/repository/maven-central/</url>
|
|
257
|
+ <releases>
|
|
258
|
+ <enabled>true</enabled>
|
|
259
|
+ </releases>
|
|
260
|
+ <snapshots>
|
|
261
|
+ <enabled>false</enabled>
|
|
262
|
+ </snapshots>
|
|
263
|
+ </repository>
|
|
264
|
+
|
|
265
|
+ <repository>
|
|
266
|
+ <id>release</id>
|
|
267
|
+ <name>Nexus Release Repository</name>
|
|
268
|
+ <url>http://117.34.118.57:28081/repository/maven-releases/</url>
|
|
269
|
+ <releases>
|
|
270
|
+ <enabled>true</enabled>
|
|
271
|
+ </releases>
|
|
272
|
+ <snapshots>
|
|
273
|
+ <enabled>false</enabled>
|
|
274
|
+ </snapshots>
|
|
275
|
+ </repository>
|
|
276
|
+
|
|
277
|
+ <repository>
|
|
278
|
+ <id>snapshots</id>
|
|
279
|
+ <name>Nexus Snapshots Repository</name>
|
|
280
|
+ <url>http://117.34.118.57:28081/repository/maven-snapshots/</url>
|
|
281
|
+ <releases>
|
|
282
|
+ <enabled>true</enabled>
|
|
283
|
+ </releases>
|
|
284
|
+ <snapshots>
|
|
285
|
+ <enabled>true</enabled>
|
|
286
|
+ </snapshots>
|
|
287
|
+ </repository>
|
|
288
|
+ </repositories>
|
333
|
289
|
|
334
|
|
- <!-- activeProfiles
|
335
|
|
- | List of profiles that are active for all builds.
|
336
|
|
- |
|
337
|
|
- <activeProfiles>
|
338
|
|
- <activeProfile>alwaysActiveProfile</activeProfile>
|
339
|
|
- <activeProfile>anotherAlwaysActiveProfile</activeProfile>
|
340
|
|
- </activeProfiles>
|
341
|
|
- -->
|
|
290
|
+ <pluginRepositories>
|
|
291
|
+ <pluginRepository>
|
|
292
|
+ <id>plugins</id>
|
|
293
|
+ <name>Nexus Plugin Repositories</name>
|
|
294
|
+ <url>http://117.34.118.57:28081/repository/maven-public/</url>
|
|
295
|
+ </pluginRepository>
|
|
296
|
+ </pluginRepositories>
|
|
297
|
+ </profile>
|
|
298
|
+ <!--
|
|
299
|
+ | Here is another profile, activated by the system property 'target-env' with a value of 'dev',
|
|
300
|
+ | which provides a specific path to the Tomcat instance. To use this, your plugin configuration
|
|
301
|
+ | might hypothetically look like:
|
|
302
|
+ |
|
|
303
|
+ | ...
|
|
304
|
+ | <plugin>
|
|
305
|
+ | <groupId>org.myco.myplugins</groupId>
|
|
306
|
+ | <artifactId>myplugin</artifactId>
|
|
307
|
+ |
|
|
308
|
+ | <configuration>
|
|
309
|
+ | <tomcatLocation>${tomcatPath}</tomcatLocation>
|
|
310
|
+ | </configuration>
|
|
311
|
+ | </plugin>
|
|
312
|
+ | ...
|
|
313
|
+ |
|
|
314
|
+ | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
|
|
315
|
+ | anything, you could just leave off the <value/> inside the activation-property.
|
|
316
|
+ |
|
|
317
|
+ <profile>
|
|
318
|
+ <id>env-dev</id>
|
|
319
|
+
|
|
320
|
+ <activation>
|
|
321
|
+ <property>
|
|
322
|
+ <name>target-env</name>
|
|
323
|
+ <value>dev</value>
|
|
324
|
+ </property>
|
|
325
|
+ </activation>
|
|
326
|
+
|
|
327
|
+ <properties>
|
|
328
|
+ <tomcatPath>/path/to/tomcat/instance</tomcatPath>
|
|
329
|
+ </properties>
|
|
330
|
+ </profile>
|
|
331
|
+ -->
|
|
332
|
+ </profiles>
|
|
333
|
+
|
|
334
|
+ <!-- activeProfiles
|
|
335
|
+ | List of profiles that are active for all builds.
|
|
336
|
+ |
|
|
337
|
+ <activeProfiles>
|
|
338
|
+ <activeProfile>alwaysActiveProfile</activeProfile>
|
|
339
|
+ <activeProfile>anotherAlwaysActiveProfile</activeProfile>
|
|
340
|
+ </activeProfiles>
|
|
341
|
+ -->
|
342
|
342
|
</settings>
|