Maven仓库

不会敲代码

已于 2023-12-04 22:32:41 修改

阅读量88

点赞数

分类专栏： SSM框架文章标签： maven java 数据库

于 2023-11-04 19:17:41 首次发布

本文链接：https://blog.csdn.net/m0_72536301/article/details/134221533

版权

SSM框架专栏收录该内容

6 篇文章 0 订阅

订阅专栏

一. 什么是Maven

下面给出官方解释:https://maven.apache.org/index.html

Apache Maven is a software project management and comprehension tool. Based on the concept of a project object model (POM), Maven can manage a project's build, reporting and documentation from a central piece of information.

直接解释就是,Maven是一个项目管理工具,通过pom.xml文件的配置来获取jar包,而不用手动添加jar包.

其实Maven提供的功能有很多,但在我们的项目中主要体现在两方面:

项目构建
管理依赖

二. 项目构建

idea内置了Maven,我们在创建项目时选择Maven项目即可

创建完项目后,来看一下目录结构.maven项目中最关键的就是pom.xml文件,它包含了这个项目的配置信息.

我们知道,在本地创建的项目,由于没有公网IP,需要把它放在一个具有公网IP的服务器上,这就需要对项目进行打包.

可以通过pom.xml来设置打包类型,在pom.xml中添加下面的标签.

<build>
        <finalName>maven</finalName><!--设置打包名称-->
    </build>
    <packaging>war</packaging><!--设置打包类型为war-->

对项目打包完成后,就会在控制台看到下图界面

这时候我们查看一下target目录,就会发现多了一个war包

三. 依赖管理

3.1 依赖配置

学过Servlet之后,我们知道要先在项目中引入servlet依赖,这时候需要先到maven中央仓库仓库找到该依赖,选择合适的版本,并引入一个dependency标签

博主引入的是3.1.0的Servlet,需要先在pom.xml中添加一个dependencies标签,然后在该标签中添加dependency标签

<dependencies>
        <!-- https://mvnrepository.com/artifact/javax.servlet/javax.servlet-api -->
        <dependency>
            <groupId>javax.servlet</groupId>
            <artifactId>javax.servlet-api</artifactId>
            <version>3.1.0</version>
            <scope>provided</scope>
        </dependency>
    </dependencies>

上面这段代码,称为"坐标",可以唯一标识一个jar包,当我们在pom.xml文件中配置完依赖后,Maven会根据坐标的配置,去仓库寻找jar包,并把它下载到项目中.

然后点击右上角的刷新标志,就可以引入这个依赖.

如果不小心把这个刷新图标关闭了,也可以按照下图步骤进行刷新

如果没有maven,我们需要用到Servlet时,就要手动下载jar包,并把这个jar包添加到项目中.

3.2 依赖传递

如果A依赖B,B依赖C,当我们使用A时,就需要把B和C都引入进来,这个过程比较麻烦,需要程序猿知道库与库之间的依赖关系.

maven的依赖具有传递性,当我们引入A时,它就会自动将A的依赖也一起导入.

3.3 依赖排除

如果发生了如上图所示的依赖关系,并且B和C引入的D.jar包不同的话,就会发生版本冲突.

maven就会主动断开依赖的资源(只会导入一个D的jar包).

3.4 Maven Helper插件

通过使用Maven Helper插件,我们就可以查看各个依赖之间的关系

安装好插件后,当我们再次打开pom.xml文件时,就可以看到如下界面

四. Maven仓库

Maven仓库分为两大类: 本地仓库和远程仓库,其中远程仓库又分为中央仓库,私服和其他仓库.

4.1 本地仓库

中央仓库全球只有一个,网址https://mvnrepository.com/

本地仓库就是自己计算机上的一个目录.

当我们引入一个jar包时,会发生下面的情况:

如果本地仓库有这个jar包,会直接导入
如果本地仓库没有,会到中央仓库寻找,找到后会拉取到本地仓库,然后导入到项目中

可以从Idea中看到本地仓库的路径,如下图

4.2 私有服务器(私服)

私服,一般是有公司或团队搭建的私有仓库.它属于某个公司或某个部门,往往需要一定的权限.

有了私服之后,jar包下载的顺序也会发生变化:

当需要下载资源的时候,先去本地仓库找
如果本地仓库没有,就会去私服找
如果私服没有,就会去中央仓库拉取,并下载到私服,本地,项目

也就是说,团队中只要有一个人引入了该依赖,私服就会下载这个jar包,以后其他人引入时就不用去中央仓库拉取了.

回到idea的setting界面,我们也可以找到私服/国内源的位置

4.3 配置国内源

因为中央仓库在国外,拉取资源时往往比较慢,我们就可以配置国内源

根据idea下的国内源路径找到.m2目录

如果没有settings.xml文档,可以创建一个,内容如下(阿里云的国内源)

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<!-- 
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.2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.2.0 https://maven.apache.org/xsd/settings-1.2.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>
   -->
<!--  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.
   | -->
<mirrors>
<!--  mirror
     | 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>
      -->
<mirror>
<id>aliyunmaven</id>
<mirrorOf>*</mirrorOf>
<name>阿里云公共仓库</name>
<url>https://maven.aliyun.com/repository/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.
   |
   | -->
<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.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>
<!--  activeProfiles
   | List of profiles that are active for all builds.
   |
  <activeProfiles>
    <activeProfile>alwaysActiveProfile</activeProfile>
    <activeProfile>anotherAlwaysActiveProfile</activeProfile>
  </activeProfiles>
   -->
</settings>

如果已经有了settings.xml,可以通过修改mirrors标签更换国内源.