企博汇java 开发环境配置

myskya

首次写于2019年12月16日
注：全部使用目前最新版本，并给出相应链接windows:windows 10专业版64位
Java版本：jdk-8u231-windows-x64.exe
maven版本：Apache Maven 3.6.3
eclipse :2019-09版
sts 4.4.2

一、安装Java环境1、下载jdk
下载地址：https://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
有可能会根据版本不同有所变化，
可以根据导航进入：

https://www.oracle.com/downloads/
在Developer Downloads找到java
点击java以后，右边会找到Java SE
点击进入后，大概在第三栏左右，有Java SE 8u231，这个数字会有细微的变化，会越变越大

点击jdk下载
2、安装jdk
我这儿把所有的java、maven、eclipse全部安装在了D盘的websrv目录下了
jdk的安装路径为：

1. d:\websrv\java\jdk

复制代码

安装过程中会有选择jre的路径，我选择安装在：

1. d:\websrv\java\jre

复制代码

因为我写的时候已经安装好了，就不再截图了
3、配置java环境
按win+E,打开资源管理器，win就是键盘左下角那个windows 图标
在左边窗口此电脑上点右键，属性
打开系统，在左边点击高级系统配置
打开系统属性窗口

点环境变量
在下面一个系统变量中增加

1. JAVA_HOME=D:\webSrv\java\jdk
   
2. CLASSPATH=.;%JAVA_HOME%\lib;%JAVA_HOME%\lib\dt.jar;%JAVA_HOME%\lib\tools.jar
   
3. path中点新增
   
4. 然后输入%JAVA_HOME%\bin
   

复制代码

此时打开WIN+R，输入cmd

1. D:\webSrv\maven\conf>java -version
   
2. <font color="#ff0000">java version "1.8.0_212"</font>
   
3. Java(TM) SE Runtime Environment (build 1.8.0_212-b10)
   
4. Java HotSpot(TM) 64-Bit Server VM (build 25.212-b10, mixed mode)

复制代码

红色部分会根据不同版本有些许变化，只要有类似的文字出现，说明java环境已经安装好了

二、安装配置maven
1、下载安装maven
下载地址：

1. https://maven.apache.org/download.cgi

复制代码

我选择的是apache-maven-3.6.3-bin.zip
下载完回来，解压缩到D:\webSrv\maven目录
另我在这个目录下新建一个目录
D:\webSrv\maven-repository，这个目录用于存放maven下载回来的jar包
2、配置maven环境变量
同1.3一样，打开系统环境变量
输入以下环境变量：

1. MAVEN_HOME=D:\webSrv\maven
   
2. MAVEN_OPTS=-Xms256m -Xmx512m -Dfile.encoding=UTF-8

复制代码

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

复制代码

主要就是加了一个：

1.   <localRepository>D:\webSrv\maven-repository</localRepository>

复制代码

和阿里云的镜像：

1. <mirror>
   
2.     <id>alimaven</id>
   
3.     <mirrorOf>central</mirrorOf>
   
4.     <name>aliyun maven</name>
   
5.     <url>http://maven.aliyun.com/nexus/content/repositories/central/</url>
   
6. </mirror>
   
7. 
   
8. <!-- 中央仓库1 -->
   
9. <mirror>
   
10.     <id>repo1</id>
    
11.     <mirrorOf>central</mirrorOf>
    
12.     <name>Human Readable Name for this Mirror.</name>
    
13.     <url>http://repo1.maven.org/maven2/</url>
    
14. </mirror>
    
15. 
    
16. <!-- 中央仓库2 -->
    
17. <mirror>
    
18.     <id>repo2</id>
    
19.     <mirrorOf>central</mirrorOf>
    
20.     <name>Human Readable Name for this Mirror.</name>
    
21.     <url>http://repo2.maven.org/maven2/</url>
    
22. </mirror>

复制代码

其余没有变动，也可能将我这个文件复制进你的文件

4、验证maven
WIN+R,输入cmd，打开dos命令窗口

1. mvn -v

复制代码

出现以下内容：

1. D:\webSrv\maven\conf>mvn -v
   
2. Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
   
3. Maven home: D:\webSrv\maven\bin\..
   
4. Java version: 1.8.0_212, vendor: Oracle Corporation, runtime: D:\webSrv\java\jdk\jre
   
5. Default locale: zh_CN, platform encoding: UTF-8
   
6. OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

复制代码

说明maven已经安装好了

三、安装运行eclipse和sts
进入网址：

1. https://www.eclipse.org/downloads/

复制代码

Get Eclipse IDE 2019‑09
下面download 64 bit
以后有可能会有变化，我写的时候是这个版本，不过最好也是使用最新版本了
点开安装的时候，出现如下图：

选择第一个就可以了

目录配置如下：
我这个图是已经安装了，所以说目录冲突而已
点install安装即可
2、配置eclipse
安装完成后，我把我的默认项目目录配置到了d:\sunprog\eclipse目录下了，你们可以随意配置
打开eclipse之后，第一步就是要配置默认工作目录，根据自己的习惯配置吧
打开程序之后，点菜单：Window->Preferences->General->workspace
左下角有Text file encoding，改成utf-8
next text file line delimiter，选择unix
如下图：

还在这个窗口，左边选择java->installed JREs ,Add，选择standard VM,点JRE HOME，选择d:\java\jre，其余不用写，最后配置成我下图样式

好像这一步是不要配置的，打开看一下般会自动选择的
还在这个窗口，打开：maven->installations，点add，选中d:\websrv\maven
配置如下图：

再选中左边的user settings


配置好这些之后
再打开菜单：
Help->Eclipse Marketplace...
打开窗口之后输入sts查询

选择spring tools 4
照着安装完成之后，重启eclipse
大功告成