精华内容
下载资源
问答
  • 2019-06-18 09:49:15

    1.更改本地仓库位置

    <!--配置本地仓库-->
    <localRepository>D:/m2/repository</localRepository>

    2.配置阿里云镜像

    <mirrors>
        <mirror>
        <!--This sends everything else to /public -->
        <id>nexus-aliyun</id>
        <mirrorOf>*</mirrorOf>
        <name>Nexus aliyun</name>
        <url>http://maven.aliyun.com/nexus/content/groups/public</url>
    	</mirror>
      </mirrors>

    3. 配置jdk1.8

    <profiles>
        <profile>  
            <id>jdk18</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> 

     

     

    更多相关内容
  • maven setting配置文件

    2017-08-11 22:51:40
    maven setting配置文件
  • 用于maven setting.xml文件丢失,eclipse集成maven插件.m2下无setting.xml文件需要配置的情况
  • 需要配置Maven阿里镜像的可以来下载,就一个积分也不贵~1.1.1.1.1.1.1.1.1.1.1.1.1.1.
  • maven配置setting文件

    2017-07-23 14:32:30
    maven的setting配置文件,收集下来共同分享
  • 每次重新下载IDEAL都有重新配置好多东西,真的挺浪费时间,这个主题也是自己选择后很喜欢的,所以决定保存下来,需要的时候只需要import就好了
  • Maven Setting配置文件,多资源库配置,包括本地和远端配置样例
  • Maven原版settings.xml配置文件,根据个人需要,可以打开对应注释或替换相关阿里云镜像或远程仓库地址即可使用。
  • IDEA settings配置文件

    2018-02-07 14:07:51
    IDEA 通用settings配置文件。导入IDEA即可。主要包括:暗黑界面风格,字体优化,eclipse快捷键,代码热部署,代码格式化等。
  • setting配置文件详解

    千次阅读 2020-07-03 22:37:08
    1. setting配置文件 setting配置文件是maven最核心的配置文件,在maven的conf目录下。 [外链图片转存失败,源站可能有防盗链机制,建议将图片保存下来直接上传(img-iST3MPFg-1593786959860)(_v_images/...

    1. setting配置文件

    setting配置文件是maven最核心的配置文件,在maven的conf目录下。
    maven目录

    1.1. 配置jdk版本

    jdk版本

    1.2. 配置下载依赖存放目录

    我的这里放置在了D://maven-repository下面
    例

    1.3. 配置国内镜像

    配置国内镜像(阿里云)相当于从外网映射到国内的网站,所以下载速度会更快。
    站,所以下载速度会更快。
    国内镜像

    展开全文
  • 阿里云最新的中央仓库地址,原先的不能用了。在这里备份一下。
  • maven配置setting.xml文件,使用阿里云下载地址

    万次阅读 多人点赞 2018-06-28 10:57:52
    | maven will use a sensible default value, perhaps based on some other setting, for | the parameter in question. | | Default: true <interactiveMode>true --> <!-- offline | Determines ...

    简简单单,直接复制过去代替掉原来的就可以使用了。

    <?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.home}/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>
      -->
    
    
      <!-- 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>
        -->
        <pluginGroup>org.mortbay.jetty</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>
        -->
        <server>
            <id>releases</id>
            <username>ali</username>
            <password>ali</password>
          </server>
          <server>
            <id>Snapshots</id>
            <username>ali</username>
            <password>ali</password>
          </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>
          <!--This sends everything else to /public -->
          <id>nexus</id>
          <mirrorOf>*</mirrorOf> 
          <url>http://maven.aliyun.com/nexus/content/groups/public/</url>
        </mirror>
        <mirror>
          <!--This is used to direct the public snapshots repo in the 
              profile below over to a different nexus group -->
          <id>nexus-public-snapshots</id>
          <mirrorOf>public-snapshots</mirrorOf> 
          <url>http://maven.aliyun.com/nexus/content/repositories/snapshots/</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>
          <id>development</id>
          <repositories>
            <repository>
              <id>central</id>
              <url>http://central</url>
              <releases><enabled>true</enabled><updatePolicy>always</updatePolicy></releases>
              <snapshots><enabled>true</enabled><updatePolicy>always</updatePolicy></snapshots>
            </repository>
          </repositories>
         <pluginRepositories>
            <pluginRepository>
              <id>central</id>
              <url>http://central</url>
              <releases><enabled>true</enabled><updatePolicy>always</updatePolicy></releases>
              <snapshots><enabled>true</enabled><updatePolicy>always</updatePolicy></snapshots>
            </pluginRepository>
          </pluginRepositories>
        </profile>
        <profile>
          <!--this profile will allow snapshots to be searched when activated-->
          <id>public-snapshots</id>
          <repositories>
            <repository>
              <id>public-snapshots</id>
              <url>http://public-snapshots</url>
              <releases><enabled>false</enabled></releases>
              <snapshots><enabled>true</enabled><updatePolicy>always</updatePolicy></snapshots>
            </repository>
          </repositories>
         <pluginRepositories>
            <pluginRepository>
              <id>public-snapshots</id>
              <url>http://public-snapshots</url>
              <releases><enabled>false</enabled></releases>
              <snapshots><enabled>true</enabled><updatePolicy>always</updatePolicy></snapshots>
            </pluginRepository>
          </pluginRepositories>
        </profile>
      </profiles>
    
       <activeProfiles>
        <activeProfile>development</activeProfile>
        <activeProfile>public-snapshots</activeProfile>
       </activeProfiles>
    </settings>
    展开全文
  • Maven setting配置文件

    万次阅读 多人点赞 2018-05-27 00:33:31
    修改maven配置文件 <profile> <id>jdk-1.8</id> <activation> <activeByDefault>true</activeByDefault> <jdk>1.8</jdk> </activation> <properties> <maven.compiler.source>1.8...


    Maven setting配置镜像仓库

    配置本地仓库

       1 <!--自定义本地仓库路径-->

      2 <localRepository>E:\JAVA\Maven</localRepository>

    国内Maven镜像仓库

    <mirror>
        <id>alimaven</id>
        <name>aliyun maven</name>
        <url>http://maven.aliyun.com/nexus/content/groups/public/</url>
        <mirrorOf>central</mirrorOf>
    </mirror>
    <mirror>
        <id>alimaven</id>
        <mirrorOf>central</mirrorOf>
        <name>aliyun maven</name>
        <url>http://maven.aliyun.com/nexus/content/repositories/central/</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>central</id>
        <name>Maven Repository Switchboard</name>
        <url>http://repo1.maven.org/maven2/</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>


    maven项目编译jdk版本更改

    首先要下载
    maven-compiler-plugin   jar包

    通过maven-compiler-plugin  jar包指定JDK版本和编码

    方法1

    在maven项目的pom.xml中加入一下代码
        <build>  
                <plugins>  
                    <plugin>  
                        <groupId>org.apache.maven.plugins</groupId>  
                        <artifactId>maven-compiler-plugin</artifactId>  
                        <version>2.1</version>  
                        <configuration>  
                            <source>1.7</source>  
                            <target>1.7</target>  
                        </configuration>  
                    </plugin>  
                </plugins>  
            </build>  


    然后重新update maven就可以解决该问题

    方法2

    修改maven配置文件

        <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>  

    然后刷新

    先右键项目 选择maven选项add plugin

    搜索compiler  选最新的

    然后强制更新项目

    完整setting配置


    1. 本地仓库路径由 .m2/repository 更改到E:\java\maven

    2.增加国内镜像仓库2个

    3.maven 编译器版本更改为javaSE-1.8

    <?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.home}/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>E:\JAVA\Maven</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>alimaven-central</id>
                <mirrorOf>central</mirrorOf>
                <name>aliyun maven</name>
                <url>http://maven.aliyun.com/nexus/content/repositories/central/</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>alimaven</id>
                <name>aliyun maven</name>
                <url>http://maven.aliyun.com/nexus/content/groups/public/</url>
                <mirrorOf>central</mirrorOf>
            </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>central</id>
                <name>Maven Repository Switchboard</name>
                <url>http://repo1.maven.org/maven2/</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>-->
    
        </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>
            -->
            <profile>
                <id>jdk18</id>
                <activation>
                    <jdk>1.8</jdk>
                    <activeByDefault>true</activeByDefault>
                </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>
    
            <!--
             | 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>
    
    


    展开全文
  • mvn 命令自定义 setting 配置文件

    千次阅读 2021-08-25 09:38:32
    mvn -s "D:\program\maven-3.6.3\maven3\conf\settings.xml" clean install
  • maven的setting.xml文件配置

    千次阅读 2019-11-26 17:38:43
    setting.xml,右击打开 2、配置本地仓库路径(默认路径为C盘下,尽量不放C盘,之后用到的依赖包非常多,所以修改路径) (1)查找"localRepository" (2)添加本地仓库路径,根据自己需求添加,格式为: D:\JAVA\...
  • 第一步: 第二步: 第三步:路径配置完毕后点击右下角“OK”按钮即OK
  • IDEA 修改 Maven 的setting配置文件指向

    千次阅读 2019-08-31 17:53:41
    使用IDEA的时候换一下 Maven的setting文件的指向。 这个需求就是,你本来使用自己...做法就是复制一份setting配置文件,找打你的maven然后存放一份复制的setting文件,然后再在IDEA里边改变一下配置文件的指向: ...
  • vscode 配置文件setting

    千次阅读 2019-10-12 10:14:41
    简单常用的插件配置,格式化,附加踩坑
  • maven 3.8.1 安装及配置文件setting.xml

    千次阅读 2021-06-25 10:02:13
    1.官网下载maven maven3.8.1链接 2.解压并修改conf文件夹下的setting.xml 3.配置环境变量 3.1此电脑->属性->高级系统设置->环境变量->系统变量(新建) 变量名:MAVEN_HOME 变量值:maven解压路径。如:D:\javaware\...
  • Maven私服配置Setting和Pom文件

    千次阅读 2020-03-17 14:22:22
    id=3688b5fa1f7d7df8b183ad8c9503546d 作者:jstarseven 上一遍博客已经在linux服务器上,搭建好nexus私服了 现在就需要配置setting.xml和pom.xml来使nexus作为maven的私服。setting.xml文件在c...
  • 这是maven 自定义仓库配置方案。本地仓库默认放在C盘,如果要想将本地仓库转移到指定到自动以的位置,就需要配置setting.xml,下载后只需修改本地仓库的配置即可!
  • Maven中setting文件配置

    千次阅读 2018-11-23 16:09:45
    maven配置文件为settings.xml,主要应用于对maven管理的项目的依赖配置进行自动更新和下载,一般情况下,maven会根据settings.xml文件给出的配置信息和url依次从本地仓库、远程仓库和中央仓库下载项目指定的依赖jar...
  • vscode setting.json文件配置

    万次阅读 2019-05-07 13:19:49
    { "search.followSymlinks": false, ... //配置下vscode支持vue语言 "eslint.validate": [ "javascript", "javascriptreact", "html", { "language": "vue", "autoFix": true } ] }
  • Maven之pom.xml与setting.xml配置文件详解

    万次阅读 2018-01-23 12:36:48
    注意:在Maven2的配置文件setting.xml一定要修改如下属性: true 该属性配置默认为false,因为是在内网,无法到外网下载依赖包,所以一定要配置离线属性为true。 3、如果本地仓库确实存在该依赖包,且eclipse没有...
  • 进入maven对应配置文件打开setting.xml文件 加入对应访问代码即可: <mirror> <id>alimaven</id> <name>aliyun maven</name> <url>http://maven.aliyun.com/nexus...
  • Maven之(六)setting.xml配置文件详解

    万次阅读 多人点赞 2016-05-24 09:51:24
    鉴于CSDN对**版权保护的不作为**以及落后的运营手段,本博客将于近期关闭,并清空全部文章。 原有文章将会经过再次的校对、整理,转移至本人在**简书**的[博客空间](https://www.jianshu.com/u/3ec23ef9a408... ...
  • MAVEN配置文件setting.xml的配置

    千次阅读 2019-05-21 14:28:12
    Maven作为项目管理工具目前已经在很多公司使用,特备是有很多大型项目上更是需要自己搭建内网私服来对项目进行单独管理,在此就几种情况下maven的setting文件配置作以区分,以备后期使用,想了解每个配置项的具体...
  • 这里写目录标题下载官网最新版本一、maven配置文件修改1、setting文件:2、环境变量配置3、idea使用中maven的配置 下载官网最新版本 http://maven.apache.org/download.cgi 一、maven配置文件修改 1、setting文件: ...
  • 读取scrapy配置文件setting.py中的方法

    千次阅读 2019-02-18 12:50:48
    from scrapy.utils.project import get_project_settings settings = get_project_settings() user_agents = settings['USER_AGENTS']  

空空如也

空空如也

1 2 3 4 5 ... 20
收藏数 253,206
精华内容 101,282
关键字:

下载setting无配置文件