Интеграция Nexus maven, получившая ошибку ниже

Question

Я использую хранилище nexus-3.0.1-01 с maven 3. Когда я попытался построить проект maven, я получаю следующую ошибку.

Плагин org.apache.maven.plugins: Maven-ресурсы-плагин: 2,5 или один из его зависимостей не может быть решена: Не удалось прочитать артефакт дескриптор для org.apache.maven.plugins: Maven -ресурсы-плагин: баночка: 2,5: Отказ найти org.apache.maven.plugins: Maven-ресурсы-плагин: П: 2,5 в http://localhost:8081/nexus/content/groups/public кэшировались в локальном хранилище, разрешение не будет повторная попытка до обновления интервал взаимосвязи, или обновления принудительно.

Settings.xml

<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>C:\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> 
      <!--This sends everything else to /public --> 
      <id>nexus</id> 
      <mirrorOf>*</mirrorOf> 
      <url>http://localhost:8081/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. 
    | 
    |--> 
    <profiles> 
     <profile> 
      <id>nexus</id> 
      <!--Enable snapshots for the built in central repo to direct --> 
      <!--all requests to nexus via the mirror --> 
      <repositories> 
       <repository> 
        <id>central</id> 
        <url>http://central</url> 
        <releases> 
         <enabled>true</enabled> 
        </releases> 
        <snapshots> 
         <enabled>true</enabled> 
        </snapshots> 
       </repository> 
      </repositories> 
      <pluginRepositories> 
       <pluginRepository> 
        <id>central</id> 
        <url>http://central</url> 
        <releases> 
         <enabled>true</enabled> 
        </releases> 
        <snapshots> 
         <enabled>true</enabled> 
        </snapshots> 
       </pluginRepository> 
      </pluginRepositories> 
     </profile> 
    </profiles> 
    <activeProfiles> 
     <!--make the profile active all the time --> 
     <activeProfile>nexus</activeProfile> 
    </activeProfiles> 
</settings> 

Answer 1

Ваш settings.xml использует неправильный URL для Maven-общественных групп. Этот URL-адрес изменился с версии 2 на версию 3.

Правильный пример можно найти в documentation или example projects.