修改Maven中conf目录里的setting.xml文件内容,加上如下内容:
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
|
<
profiles
>
<!-- 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.8</
id
>
<
activation
>
<
activeByDefault
>true</
activeByDefault
>
<
jdk
>1.8</
jdk
>
</
activation
>
<
properties
>
<
maven.compiler.source
>1.8</
maven.compiler.source
>
<
maven.compiler.target
>1.8</
maven.compiler.target
>
<
maven.compiler.compilerVersion
>1.8</
maven.compiler.compilerVersion
>
</
properties
>
<
repositories
>
<
repository
>
<
id
>nexus</
id
>
<
name
>local private nexus</
name
>
<
url
>http://maven.oschina.net/content/groups/public/</
url
>
<
releases
>
<
enabled
>true</
enabled
>
</
releases
>
<
snapshots
>
<
enabled
>false</
enabled
>
</
snapshots
>
</
repository
>
</
repositories
>
<
pluginRepositories
>
<
pluginRepository
>
<
id
>nexus</
id
>
<
name
>local private nexus</
name
>
<
url
>http://maven.oschina.net/content/groups/public/</
url
>
<
releases
>
<
enabled
>true</
enabled
>
</
releases
>
<
snapshots
>
<
enabled
>false</
enabled
>
</
snapshots
>
</
pluginRepository
>
</
pluginRepositories
>
</
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> -->
</
profiles
>
|