阅读 127

maven 项目 maven setting.xml 配置 maven 项目 初始 办的一些事,以及一些采坑记录

目录

1.介绍

2.下载地址

2.1放到本地一个位置,解压

2.2配置eclipse 配置 

3.setting.xml 配置

3.1本地lib包等jar 放到哪里

3.2配置拉取库自定义一个国内的

3.3配置jdk

方案一

方案二

方案三

3.4完整的一个配置

3.5国内一些较快的maven 库

maven.aliyun.com

4.配置环境变量

4.1配置 maven_home

4.2配置 path

5.cmd  测试 mvn 环境变量配置情况

6.eclipse  配置

6.1不要下载一些没用的东西  doc

6.2eclipse JDK 配置 maven 

maven 简单报错解决办法

Multiple annotations found at this line:    - ArtifactTransferException: Failure to transfer org.apache.ant:ant:jar:1.8.2 from http://maven.aliyun.com/nexus/content/groups/public/ was cached in the local      repository, resolution will not be reattempted until the update interval of alimaven has elapsed or updates are forced. Original error: Could not transfer artifact      org.apache.ant:ant:jar:1.8.2 from/to alimaven (http://maven.aliyun.com/nexus/content/groups/public/): No route to host: connect    - ArtifactTransferException: Failure to transfer org.apache.ant:ant-launcher:jar:1.8.2 from http://maven.aliyun.com/nexus/content/groups/public/ was cached in      the local repository, resolution will not be reattempted until the update interval of alimaven has elapsed or updates are forced. Original error: Could not transfer artifact      org.apache.ant:ant-launcher:jar:1.8.2 from/to alimaven (http://maven.aliyun.com/nexus/content/groups/public/): No route to host: connect    - ArtifactTransferException: Failure to transfer org.apache.xmlbeans:xmlbeans:jar:2.6.0 from http://maven.aliyun.com/nexus/content/groups/public/ was cached in      the local repository, resolution will not be reattempted until the update interval of alimaven has elapsed or updates are forced. Original error: Could not transfer artifact      org.apache.xmlbeans:xmlbeans:jar:2.6.0 from/to alimaven (http://maven.aliyun.com/nexus/content/groups/public/): No route to host: connect

看好这里 这是重点






1.介绍

记录下maven 配置和下载,方便使用。

 

2.下载地址

maven.apache.org/download.ht…

 

2.1放到本地一个位置,解压

 

2.2配置eclipse 配置 

blog.csdn.net/weixin_4274…

 

 

3.setting.xml 配置

 

3.1本地lib包等jar 放到哪里

<localRepository>D:\kf\apache-maven-3.6.3-bin\apache-maven-3.6.3\maven_repository</localRepository>
复制代码

 

3.2配置拉取库自定义一个国内的

<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>
     -->
	 
		<id>nexus-aliyun</id>
		<mirrorOf>*</mirrorOf>
		<name>Nexus aliyun</name>
		<url>http://maven.aliyun.com/nexus/content/groups/public</url>
  </mirrors>
复制代码

 

3.3配置jdk

方案一

 <profiles>
        <profile>
            <id>jdk-15.0.2</id>
            <activation>
                <activeByDefault>true</activeByDefault>
                <jdk>15.0.2</jdk>
            </activation>
 
            <properties>
                <maven.compiler.source>15.0.2</maven.compiler.source>
                <maven.compiler.target>15.0.2</maven.compiler.target>
                <maven.compiler.compilerVersion>15.0.2</maven.compiler.compilerVersion>
            </properties>
        </profile>
    </profiles>
复制代码

 

方案二

<profile>   
    <id>jdk1.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> 
复制代码

 

方案三

<profile>
            <id>custom-compiler</id>
            <properties>
                <JAVA8_HOME>C:\Program Files\Java\jdk1.8.0_131</JAVA8_HOME>
            </properties>
</profile>
复制代码

 

3.4完整的一个配置

<?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>D:\kf\apache-maven-3.6.3-bin\apache-maven-3.6.3\maven_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.
   |-->
  <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>
     -->
	 
		<id>nexus-aliyun</id>
		<mirrorOf>*</mirrorOf>
		<name>Nexus aliyun</name>
		<url>http://maven.aliyun.com/nexus/content/groups/public</url>
  </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>
    -->
    <profiles>
        <profile>
            <id>jdk-15.0.2</id>
            <activation>
                <activeByDefault>true</activeByDefault>
                <jdk>15.0.2</jdk>
            </activation>
 
            <properties>
                <maven.compiler.source>15.0.2</maven.compiler.source>
                <maven.compiler.target>15.0.2</maven.compiler.target>
                <maven.compiler.compilerVersion>15.0.2</maven.compiler.compilerVersion>
            </properties>
        </profile>
    </profiles>
    <!--
     | 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>
复制代码

 

3.5国内一些较快的maven 库

 
<mirror>  
      <id>CN</id>  
      <name>OSChina Central</name>                                                                                                                         
      <url>http://maven.oschina.net/content/groups/public/</url>  
      <mirrorOf>central</mirrorOf>  
</mirror>  
  

<mirror>    
      <id>repo2</id>    
      <mirrorOf>central</mirrorOf>    
      <name>Human Readable Name for this Mirror.</name>    
      <url>http://repo2.maven.org/maven2/</url>    
</mirror>    
<mirror>    
      <id>net-cn</id>    
      <mirrorOf>central</mirrorOf>    
      <name>Human Readable Name for this Mirror.</name>    
      <url>http://maven.net.cn/content/groups/public/</url>     
</mirror>    
<mirror>    
      <id>ui</id>    
      <mirrorOf>central</mirrorOf>    
      <name>Human Readable Name for this Mirror.</name>    
     <url>http://uk.maven.org/maven2/</url>    
</mirror>    
<mirror>    
      <id>ibiblio</id>    
      <mirrorOf>central</mirrorOf>    
      <name>Human Readable Name for this Mirror.</name>    
     <url>http://mirrors.ibiblio.org/pub/mirrors/maven2/</url>    
</mirror>    
<mirror>    
      <id>jboss-public-repository-group</id>    
      <mirrorOf>central</mirrorOf>    
      <name>JBoss Public Repository Group</name>    
     <url>http://repository.jboss.org/nexus/content/groups/public</url>    
</mirror>  
  
  
<mirror>    
      <id>JBossJBPM</id>   
    <mirrorOf>central</mirrorOf>   
    <name>JBossJBPM Repository</name>   
    <url>https://repository.jboss.org/nexus/content/repositories/releases/</url>  
</mirror>  
-------------------------spring maven--------------------------------  
http://maven.springframework.org/release/  
---------------------------------------------------------------------  
http://maven.antelink.com/content/repositories/central/  
http://nexus.openkoala.org/nexus/content/groups/Koala-release/  
http://maven.tmatesoft.com/content/groups/public/  
http://mavensync.zkoss.org/maven2/  
复制代码

 

maven.aliyun.com

<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>alimaven</id>
      <name>aliyun maven</name>
      <url>http://maven.aliyun.com/nexus/content/groups/public/</url>
      <mirrorOf>central</mirrorOf>        
    </mirror> 
  </mirrors>
复制代码

 

4.配置环境变量

4.1配置 maven_home

 

4.2配置 path

 

 

5.cmd  测试 mvn 环境变量配置情况

 

 

6.eclipse  配置

6.1不要下载一些没用的东西  doc

  • 把这玩意勾勾去掉
  • Globa Checksum Policy  全球校验和激化
  • 选择 ignore  忽略 的意思

 

 

6.2eclipse JDK 配置 maven 

  • -Dmaven.multiModuleProjectDirectory=$MAVEN_HOME
  • 或这样的
  • -Dmaven.multiModuleProjectDirectory=$MAVEN_HOME-Xms1024m -Xmx1024m
  • 这玩意jvm 就通过后边的 -Xms 等配置即可
  • 配置这玩意防止,启动springboot 项目的时候提示找不到启动类问题
  • 如下边这个截图

 

maven 简单报错解决办法

Multiple annotations found at this line:     - ArtifactTransferException: Failure to transfer org.apache.ant:ant:jar:1.8.2 from maven.aliyun.com/nexus/conte… was cached in the local       repository, resolution will not be reattempted until the update interval of alimaven has elapsed or updates are forced. Original error: Could not transfer artifact       org.apache.ant:ant:jar:1.8.2 from/to alimaven (http://maven.aliyun.com/nexus/content/groups/public/): No route to host: connect     - ArtifactTransferException: Failure to transfer org.apache.ant:ant-launcher:jar:1.8.2 from http://maven.aliyun.com/nexus/content/groups/public/ was cached in       the local repository, resolution will not be reattempted until the update interval of alimaven has elapsed or updates are forced. Original error: Could not transfer artifact       org.apache.ant:ant-launcher:jar:1.8.2 from/to alimaven (http://maven.aliyun.com/nexus/content/groups/public/): No route to host: connect     - ArtifactTransferException: Failure to transfer org.apache.xmlbeans:xmlbeans:jar:2.6.0 from http://maven.aliyun.com/nexus/content/groups/public/ was cached in       the local repository, resolution will not be reattempted until the update interval of alimaven has elapsed or updates are forced. Original error: Could not transfer artifact       org.apache.xmlbeans:xmlbeans:jar:2.6.0 from/to alimaven (http://maven.aliyun.com/nexus/content/groups/public/): No route to host: connect

 

  • 这个解决办法就是右击项目 然后 更新 maven ,如下即可

 

看好这里 这是重点

  • 有的时候 更新项目也没好,是因为 网络等各种原因
  • maven下载 jar 的时候没有下载下来,所以报红色的
  • 这时候可以进入1
  • 二 看如下爆红的jar
  • 我这里爆红叉的都解决了没显示
  • 一般会提示出红色的x 就是这个jar 没下载下来,多半是下载中途网络等各种原因断掉了
  • 这时候就要
  • 去到本地maven 库 依赖文件夹下,将这个jar 的目录删除掉
  • 然后刷新下 pom.xml  继续下载,这个缺少的jar
  • 下载下来就好了
  • 然后更新下maven 项目就好了
  • ok

 

 

 

 

.

 

 

 

 

 

 

ok

 

 

 

 

 

持续更新

 

 

 

 

 

 

 

文章分类
后端
文章标签