一、安装本地Maven
 
 
 
tips: 官网为外网，下载速度较慢，这里提供3.6.3版本的三方链接下载Maven下载
 
 
 
无视下载速度以及需要其他版本的伙伴点此进入Maven官网下载
 
 
选择左侧Download
 
 
 
点击箭头所指的链接进行下载
 
 
 
下载完成后，选择一个路径进行解压
 
 
然后配置path环境变量,如图
 
 
系统变量:MAVEN_HOME = F:\dev\apache-maven-3.6.1
系统变量:path = %MAVEN_HOME%\bin
 MAVEN_HOME:
 
 
 
path:
 
 
然后win+R 运行cmd 输入 mvn -version，如图所示则配置成功
 
 
二、配置settings文件
 
 
在F:\dev\apache-maven-3.6.1\conf下可以找到settings文件，打开(嫌麻烦的直接看最后一步)
 
 
找到第52行，这里是maven默认的仓库
 
 
 
我们复制第53行
 
 
<localRepository>/path/to/local/repo</localRepository>
 
将它拿到注释外并将中间的内容改成你需要的路径，如图
 
<localRepository>F:/repository</localRepository>
 
这里的路径随便设置，注意这里是正斜杠
 
 
因为国外的服务器下载jar包很慢所以我们改为阿里云服务器（大约在150行左右），这两个仓库只用选一个(根据大家反馈建议使用第一个，第二个在有的版本可能会出现warning)
 
 <!-- 阿里云仓库 -->
        <mirror>
            <id>alimaven</id>
            <mirrorOf>central</mirrorOf>
            <name>aliyun maven</name>
            <url>http://maven.aliyun.com/nexus/content/repositories/central/</url>
        </mirror>
     或者
      <mirror>
		<id>nexus-aliyun</id>
		<mirrorOf>*</mirrorOf>
        <name>Nexus aliyun</name>
        <url>http://maven.aliyun.com/nexus/content/groups/public</url>
	 </mirror>

 
 
如图，要夹在两个mirrors标签之间
 
 
 
在最后配置jdk，也要夹在两个profiles标签之间(我这里使用的为jdk8)
 
 
<!-- java版本 --> 
<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>
</profile>

 
 
 
配置完成，在命令行输入mvn help:system测试，看到下载链接里面是ailiyun的链接表示配置成功
 
 
嫌麻烦的直接复制配置文件的内容即可,不过路径还是要改(参考第3步)
 
 
<?xml version="1.0" encoding="UTF-8"?>

<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.
-->

<!--
 | This is the configuration file for Maven. It can be specified at two levels:
 |
 |  1. User Level. This settings.xml file provides configuration for a single user,
 |                 and is normally provided in ${user.home}/.m2/settings.xml.
 |
 |                 NOTE: This location can be overridden with the CLI option:
 |
 |                 -s /path/to/user/settings.xml
 |
 |  2. Global Level. This settings.xml file provides configuration for all Maven
 |                 users on a machine (assuming they're all using the same Maven
 |                 installation). It's normally provided in
 |                 ${maven.conf}/settings.xml.
 |
 |                 NOTE: This location can be overridden with the CLI option:
 |
 |                 -gs /path/to/global/settings.xml
 |
 | The sections in this sample file are intended to give you a running start at
 | getting the most out of your Maven installation. Where appropriate, the default
 | values (values used when the setting is not specified) are provided.
 |
 |-->
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
          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">
  <!-- localRepository
   | The path to the local repository maven will use to store artifacts.
   |
   | Default: ${user.home}/.m2/repository
  <localRepository>/path/to/local/repo</localRepository>
  -->
<localRepository>F:/repository</localRepository>
  <!-- interactiveMode
   | This will determine whether maven prompts you when it needs input. If set to false,
   | maven will use a sensible default value, perhaps based on some other setting, for
   | the parameter in question.
   |
   | Default: true
  <interactiveMode>true</interactiveMode>
  -->

  <!-- offline
   | Determines whether maven should attempt to connect to the network when executing a build.
   | This will have an effect on artifact downloads, artifact deployment, and others.
   |
   | Default: false
  <offline>false</offline>
  -->

  <!-- pluginGroups
   | This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.
   | when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers
   | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.
   |-->
  <pluginGroups>
    <!-- pluginGroup
     | Specifies a further group identifier to use for plugin lookup.
    <pluginGroup>com.your.plugins</pluginGroup>
    -->
  </pluginGroups>

  <!-- proxies
   | This is a list of proxies which can be used on this machine to connect to the network.
   | Unless otherwise specified (by system property or command-line switch), the first proxy
   | specification in this list marked as active will be used.
   |-->
  <proxies>
    <!-- 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>
    -->
  </proxies>

  <!-- servers
   | This is a list of authentication profiles, keyed by the server-id used within the system.
   | Authentication profiles can be used whenever maven must make a connection to a remote server.
   |-->
  <servers>
    <!-- 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>
    -->
  </servers>

  <!-- mirrors
   | This is a list of mirrors to be used in downloading artifacts from remote repositories.
   |
   | It works like this: a POM may declare a repository to use in resolving certain artifacts.
   | However, this repository may have problems with heavy traffic at times, so people have mirrored
   | it to several places.
   |
   | That repository definition will have a unique id, so we can create a mirror reference for that
   | repository, to be used as an alternate download site. The mirror site will be the preferred
   | server for that repository.
   |-->
  
    <!-- mirror
	<mirrors>
     | 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>
	 </mirrors>
     -->
     <!-- 阿里云仓库 -->
 <mirrors>
	 <mirror>
			<id>nexus-aliyun</id>
			<mirrorOf>*</mirrorOf>
			<name>Nexus aliyun</name>
			<url>http://maven.aliyun.com/nexus/content/groups/public</url>
	</mirror>
</mirrors>
  <!-- profiles
   | This is a list of profiles which can be activated in a variety of ways, and which can modify
   | the build process. Profiles provided in the settings.xml are intended to provide local machine-
   | specific paths and repository locations which allow the build to work in the local environment.
   |
   | For example, if you have an integration testing plugin - like cactus - that needs to know where
   | your Tomcat instance is installed, you can provide a variable here such that the variable is
   | dereferenced during the build process to configure the cactus plugin.
   |
   | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
   | section of this document (settings.xml) - will be discussed later. Another way essentially
   | relies on the detection of a system property, either matching a particular value for the property,
   | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
   | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
   | Finally, the list of active profiles can be specified directly from the command line.
   |
   | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
   |       repositories, plugin repositories, and free-form properties to be used as configuration
   |       variables for plugins in the POM.
   |
   |-->
    <!-- profile
	<profiles>
     | 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>jdk14</id>
          <name>Repository for JDK 1.4 builds</name>
          <url>http://www.myhost.com/maven/jdk14</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>
	  
    -->
<profiles>
<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>
</profile>
</profiles>



  <!-- activeProfiles
   | List of profiles that are active for all builds.
   |
  <activeProfiles>
    <activeProfile>alwaysActiveProfile</activeProfile>
    <activeProfile>anotherAlwaysActiveProfile</activeProfile>
  </activeProfiles>
  -->
</settings>

1. 下载Maven
 官方地址：http://maven.apache.org/download.cgi
 
 
解压并新建一个本地仓库文件夹
 
 
2.配置本地仓库路径
 
 
 
3.配置maven环境变量
 

 
 
 
 
 
4.在IntelliJ IDEA中配置maven
 打开-File-Settings
 
 
5.新建maven WEB项目
 打开-File-New-Project
 点击NEXT
 
 点击NEXT
 
 添加的配置为 archetypeCatalog=internal
 点击NEXT
 
 点击NEXT
 
 点击Finish后项目开始创建
 点击右下角查看进去
 
 
6.maven web模板项目结构
 
 
 

 同样在main下新建test测试文件夹,再在此文件夹下新建java测试源码文件夹和resource测试资源文件夹
 
 也可以右键项目-选择Open Module Settings打开项目配置页面更改
 
 
7.配置依赖jar包
 
 
jar包配置搜索
 官方地址：http://mvnrepository.com/
 
其它推荐
 Vue表单设计器

设备：Windows10，git(MINGW64)
 

一般刚安装Git都要配置用户名和邮箱，因为你提交代码到本地仓库（上传代码到远程仓库）时会用到，如果没有没有配置，在你提交时它会提醒你的。
 
那么接下来我们讲一下怎么配置：
 

目录
 
1、查看git的配置列表
 
2、进行配置
 
（1）命令行配置
 
补充：(1.1) 全局变量
 
    （1.2）局部变量
 
注意：局部变量覆盖全局变量！！！和编程语言里面的变量关系是一样的。
 
（2）修改对应文件进行配置
 
3、修改已配置的信息
 
（1）用命令修改
 
（2）修改对应文件进行修改
 
4、git config命令的功能列表
 
（1）git config
 
（2）git config --help
 

1、查看git的配置列表
 
我们可以先查看一下git的配置列表：
 
 
 
git config --list
 
 
如果没有配置东西，应该是空的。照着下面配置完成后，你可以再试一下该命令，就会出现一系列配置信息。
 
 
 
2、进行配置
 
（1）命令行配置
 
 
 
git config --global user.name  "username"  
 git config --global user.email  "email"
 
 
将username和email换成github（或者其它类似远程仓库）的用户名和邮箱。
 
补充：(1.1) 全局变量
 
 --global  表示全局的，即当前用户都有效，该配置会出现在 ~/.gitconfig 文件中，~表示当前用户的目录，比如我的是：C:\Users\username\.gitconfig ，打开该文件你会发现如下图所示的内容：
 
 
对比一下，你应该就知道上面的配置命令是怎么起作用的吧（其它配置命令也是这个意思！）。（注：该文件#开头的行是注释，为了方便理解，你可以自己添加一些注释信息）
 
 
    （1.2）局部变量
 
既然有全局的，那么肯定有局部的啊！局部的是不加 --global 的，如下：
 
 
 
git config  user.name  "username"  
 git config  user.email  "email"
 
 
局部是只对当前仓库起效的，它的配置信息会在当前仓库根目录/.git/config文件下：
 
 
 
 
注意：局部变量覆盖全局变量！！！和编程语言里面的变量关系是一样的。
 
我在上面我新建的那个仓库里，随便提交了一点东西，然后查看提交日志如下：
 
 
 
 
（2）修改对应文件进行配置
 
相信看了上面的补充内容之后，你应该已经了解这两个配置命令的作用了吧，所以这里就不详讲了，你找到对应文件，该相关设置就好了。
 
 
 
3、修改已配置的信息
 
假如配置后，发现有信息配置错了，如何进行修改？
 
（1）用命令修改
 
这里演示修改本地仓库的用户名和邮箱：
 
 
 
git config --replace-all user.name "name"
 
 
git config --replace-all user.email "123@qq.com"
 
 
修改后是这样的：
 
 
 
 
（2）修改对应文件进行修改
 
这个应该不用讲了。
 
 
 
4、git config命令的功能列表
 
（1）git config
 
我们直接输入git config，就可以看到简单的命令列表了：
 
$ git config
usage: git config [<options>]

Config file location
    --global              use global config file
    --system              use system config file
    --local               use repository config file
    --worktree            use per-worktree config file
    -f, --file <file>     use given config file
    --blob <blob-id>      read config from given blob object

Action
    --get                 get value: name [value-regex]
    --get-all             get all values: key [value-regex]
    --get-regexp          get values for regexp: name-regex [value-regex]
    --get-urlmatch        get value specific for the URL: section[.var] URL
    --replace-all         replace all matching variables: name value [value_regex]
    --add                 add a new variable: name value
    --unset               remove a variable: name [value-regex]
    --unset-all           remove all matches: name [value-regex]
    --rename-section      rename section: old-name new-name
    --remove-section      remove a section: name
    -l, --list            list all
    -e, --edit            open an editor
    --get-color           find the color configured: slot [default]
    --get-colorbool       find the color setting: slot [stdout-is-tty]

Type
    -t, --type <>         value is given this type
    --bool                value is "true" or "false"
    --int                 value is decimal number
    --bool-or-int         value is --bool or --int
    --path                value is a path (file or directory name)
    --expiry-date         value is an expiry date

Other
    -z, --null            terminate values with NUL byte
    --name-only           show variable names only
    --includes            respect include directives on lookup
    --show-origin         show origin of config (file, standard input, blob, command line)
    --default <value>     with --get, use default value when missing entry
 
（2）git config --help
 
这个命令默认打开本地git安装目录下的G:\Git\mingw64\share\doc\git-doc\下的详细的说明文档（这里G:\Git为安装目录），这个是详细介绍命令的作用（上面的那个只是简介）。
 
样例截图：
 
 
延伸：其它命令你也可以通过添加  --help 参数来打开命令的相关文档说明，如 git diff --help，……
 

2021年3月18日14:53:50 更新
 
之前文章名为“Git配置用户名和密码”，这个有问题的，因为git其实并没有密码，有密码的是git远程仓库，比如github，因此在此进行更正。
 
end.

 
目录
 
1、网络配置
 
2、网卡与DNS配置
 

1、网络配置
 
1 首先打开虚拟网络编辑器进行配置，会加载几秒钟
 
2 点击更改设置
 
1.3 选择添加网络，添加一个Vment0，并设置为桥接模式，桥接到 处设置为自动即可，如下图所示
 
 
注意：这里有可能会出现问题：无法将网络更改为桥接状态，没有未桥接的主机网络适配器，解决办法请查看我的另外一章博客：https://blog.csdn.net/weixin_42108484/article/details/82700740
 
1.4 将网络适配器设置为桥接状态
 
 
 
 
2、网卡与DNS配置
 
1）打开命令窗口（右键单机桌面选择Open Terminal或者Ctrl+Alt+T），输入ip a查看自己的网卡编号
 
 
3）输入命令sudo vi /etc/network/interfaces，编辑该文件。注意此处eth0处用自己的网卡编号替换，address和gateway也是要视情况定的。
 
 
编辑完成后按esc（键盘左上角那个），再输入:wq!就可以保存退出了，此时ping一些自己的内网应该是可以ping通的了。Ping www.baidu.com还是ping不通的，接下来就需要继续接着做。
 
4）在命令行输入sudo vi /etc/systemd/resolved.conf 修改改文件：将DNS前的#号去掉，然后加上通用的DNS服务器地址即可。大家可以自行上网找，也可以就和我一样配置。
 
 
5）重启网络服务：
 
      sudo /etc/init.d/networking force-reload  ==> 重新加载网路配置文件
 
      sudo /etc/init.d/networking restart
 
6）重启Ubuntu，就能ping通百度了。
 
 
7、如果正常配置出错（异常）
 
使用动态分配DNS：sudo dhclient linux动态分配IP
 
配置完成之后通过：ping www.baidu.com
 
一般而言这样就可以了，但是如果还不行，尝试如下操作：
 
①重新启停以太网卡：
 
   sudo ifconfig eth0 down
 
   sudo ifconfig eth0 up
 
②添加默认网关：
 
   sudo route add default gw 192.168.1.1
 
③检查你的网线是否已经插好了！（注意这其实是第一步！！！！！）
 
当你的网络联通之后，使用APT软件管理器
 
下载ssh/tree/vim/tftpd-hpa/nfs-kernel-server试试。