1 IntelliJ IDEA 安装
下载地址：点击前往
注意：需要下载专业版本的，注册码在网上随便搜一个就行啦
2 MAVEN工具的安装
2.1 获取安装包
下载地址：点击前往
2.2 安装过程
到官网下载的maven是绿色版的，无需安装，解压即可
2.3 修改maven的配置
2.3.1 配置maven的本地仓库路径
<localRepository>D://PTool/maven/apache-maven-3.5.0/conf/bdck</localRepository>
2.3.2 配置maven的远程仓库地址
<mirror> <id>aliyun</id> <name>aliyun Maven</name> <mirrorOf>*</mirrorOf> <url>http://maven.aliyun.com/nexus/content/groups/public/</url> </mirror>
注意：这两个配置都只需要在setting.xml中设置就可以啦
1 <?xml version="1.0" encoding="UTF-8"?> 2 3 <!-- 4 Licensed to the Apache Software Foundation (ASF) under one 5 or more contributor license agreements. See the NOTICE file 6 distributed with this work for additional information 7 regarding copyright ownership. The ASF licenses this file 8 to you under the Apache License, Version 2.0 (the 9 "License"); you may not use this file except in compliance 10 with the License. You may obtain a copy of the License at 11 12 http://www.apache.org/licenses/LICENSE-2.0 13 14 Unless required by applicable law or agreed to in writing, 15 software distributed under the License is distributed on an 16 "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY 17 KIND, either express or implied. See the License for the 18 specific language governing permissions and limitations 19 under the License. 20 --> 21 22 <!-- 23 | This is the configuration file for Maven. It can be specified at two levels: 24 | 25 | 1. User Level. This settings.xml file provides configuration for a single user, 26 | and is normally provided in ${user.home}/.m2/settings.xml. 27 | 28 | NOTE: This location can be overridden with the CLI option: 29 | 30 | -s /path/to/user/settings.xml 31 | 32 | 2. Global Level. This settings.xml file provides configuration for all Maven 33 | users on a machine (assuming they're all using the same Maven 34 | installation). It's normally provided in 35 | ${maven.home}/conf/settings.xml. 36 | 37 | NOTE: This location can be overridden with the CLI option: 38 | 39 | -gs /path/to/global/settings.xml 40 | 41 | The sections in this sample file are intended to give you a running start at 42 | getting the most out of your Maven installation. Where appropriate, the default 43 | values (values used when the setting is not specified) are provided. 44 | 45 |--> 46 <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" 47 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 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://PTool/maven/apache-maven-3.5.0/conf/bdck</localRepository> 56 57 58 <!-- interactiveMode 59 | This will determine whether maven prompts you when it needs input. If set to false, 60 | maven will use a sensible default value, perhaps based on some other setting, for 61 | the parameter in question. 62 | 63 | Default: true 64 <interactiveMode>true</interactiveMode> 65 --> 66 67 <!-- offline 68 | Determines whether maven should attempt to connect to the network when executing a build. 69 | This will have an effect on artifact downloads, artifact deployment, and others. 70 | 71 | Default: false 72 <offline>false</offline> 73 --> 74 75 <!-- pluginGroups 76 | This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e. 77 | when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers 78 | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list. 79 |--> 80 <pluginGroups> 81 <!-- pluginGroup 82 | Specifies a further group identifier to use for plugin lookup. 83 <pluginGroup>com.your.plugins</pluginGroup> 84 --> 85 </pluginGroups> 86 87 <!-- proxies 88 | This is a list of proxies which can be used on this machine to connect to the network. 89 | Unless otherwise specified (by system property or command-line switch), the first proxy 90 | specification in this list marked as active will be used. 91 |--> 92 <proxies> 93 <!-- proxy 94 | Specification for one proxy, to be used in connecting to the network. 95 | 96 <proxy> 97 <id>optional</id> 98 <active>true</active> 99 <protocol>http</protocol> 100 <username>proxyuser</username> 101 <password>proxypass</password> 102 <host>proxy.host.net</host> 103 <port>80</port> 104 <nonProxyHosts>local.net|some.host.com</nonProxyHosts> 105 </proxy> 106 --> 107 </proxies> 108 109 <!-- servers 110 | This is a list of authentication profiles, keyed by the server-id used within the system. 111 | Authentication profiles can be used whenever maven must make a connection to a remote server. 112 |--> 113 <servers> 114 <!-- server 115 | Specifies the authentication information to use when connecting to a particular server, identified by 116 | a unique name within the system (referred to by the 'id' attribute below). 117 | 118 | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are 119 | used together. 120 | 121 <server> 122 <id>deploymentRepo</id> 123 <username>repouser</username> 124 <password>repopwd</password> 125 </server> 126 --> 127 128 <!-- Another sample, using keys to authenticate. 129 <server> 130 <id>siteServer</id> 131 <privateKey>/path/to/private/key</privateKey> 132 <passphrase>optional; leave empty if not used.</passphrase> 133 </server> 134 --> 135 </servers> 136 137 <!-- mirrors 138 | This is a list of mirrors to be used in downloading artifacts from remote repositories. 139 | 140 | It works like this: a POM may declare a repository to use in resolving certain artifacts. 141 | However, this repository may have problems with heavy traffic at times, so people have mirrored 142 | it to several places. 143 | 144 | That repository definition will have a unique id, so we can create a mirror reference for that 145 | repository, to be used as an alternate download site. The mirror site will be the preferred 146 | server for that repository. 147 |--> 148 <mirrors> 149 <!-- mirror 150 | Specifies a repository mirror site to use instead of a given repository. The repository that 151 | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used 152 | for inheritance and direct lookup purposes, and must be unique across the set of mirrors. 153 | 154 <mirror> 155 <id>mirrorId</id> 156 <mirrorOf>repositoryId</mirrorOf> 157 <name>Human Readable Name for this Mirror.</name> 158 <url>http://my.repository.com/repo/path</url> 159 </mirror> 160 --> 161 <mirror> 162 <id>aliyun</id> 163 <name>aliyun Maven</name> 164 <mirrorOf>*</mirrorOf> 165 <url>http://maven.aliyun.com/nexus/content/groups/public/</url> 166 </mirror> 167 </mirrors> 168 169 <!-- profiles 170 | This is a list of profiles which can be activated in a variety of ways, and which can modify 171 | the build process. Profiles provided in the settings.xml are intended to provide local machine- 172 | specific paths and repository locations which allow the build to work in the local environment. 173 | 174 | For example, if you have an integration testing plugin - like cactus - that needs to know where 175 | your Tomcat instance is installed, you can provide a variable here such that the variable is 176 | dereferenced during the build process to configure the cactus plugin. 177 | 178 | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles 179 | section of this document (settings.xml) - will be discussed later. Another way essentially 180 | relies on the detection of a system property, either matching a particular value for the property, 181 | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a 182 | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'. 183 | Finally, the list of active profiles can be specified directly from the command line. 184 | 185 | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact 186 | repositories, plugin repositories, and free-form properties to be used as configuration 187 | variables for plugins in the POM. 188 | 189 |--> 190 <profiles> 191 <!-- profile 192 | Specifies a set of introductions to the build process, to be activated using one or more of the 193 | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/> 194 | or the command line, profiles have to have an ID that is unique. 195 | 196 | An encouraged best practice for profile identification is to use a consistent naming convention 197 | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc. 198 | This will make it more intuitive to understand what the set of introduced profiles is attempting 199 | to accomplish, particularly when you only have a list of profile id's for debug. 200 | 201 | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo. 202 <profile> 203 <id>jdk-1.4</id> 204 205 <activation> 206 <jdk>1.4</jdk> 207 </activation> 208 209 <repositories> 210 <repository> 211 <id>jdk14</id> 212 <name>Repository for JDK 1.4 builds</name> 213 <url>http://www.myhost.com/maven/jdk14</url> 214 <layout>default</layout> 215 <snapshotPolicy>always</snapshotPolicy> 216 </repository> 217 </repositories> 218 </profile> 219 --> 220 221 <!-- 222 | Here is another profile, activated by the system property 'target-env' with a value of 'dev', 223 | which provides a specific path to the Tomcat instance. To use this, your plugin configuration 224 | might hypothetically look like: 225 | 226 | ... 227 | <plugin> 228 | <groupId>org.myco.myplugins</groupId> 229 | <artifactId>myplugin</artifactId> 230 | 231 | <configuration> 232 | <tomcatLocation>${tomcatPath}</tomcatLocation> 233 | </configuration> 234 | </plugin> 235 | ... 236 | 237 | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to 238 | anything, you could just leave off the <value/> inside the activation-property. 239 | 240 <profile> 241 <id>env-dev</id> 242 243 <activation> 244 <property> 245 <name>target-env</name> 246 <value>dev</value> 247 </property> 248 </activation> 249 250 <properties> 251 <tomcatPath>/path/to/tomcat/instance</tomcatPath> 252 </properties> 253 </profile> 254 --> 255 </profiles> 256 257 <!-- activeProfiles 258 | List of profiles that are active for all builds. 259 | 260 <activeProfiles> 261 <activeProfile>alwaysActiveProfile</activeProfile> 262 <activeProfile>anotherAlwaysActiveProfile</activeProfile> 263 </activeProfiles> 264 --> 265 </settings>