我希望修改现有的Atlassian Bamboo .Net插件：https://bitbucket.org/atlassian/bamboo-dotnet-plugin，以便MsTest Parser包含StackTrace信息。
我已经在本地下载了存储库，并且我尝试使用Maven命令安装所有项目依赖项：mvn clean install -U。
不幸的是并非所有的jar都被下载了，所以我在网上寻求帮助，发现通过使用Atlassian SDK，我可以构建项目并让它处理所有maven的东西，因为它已经在settings.xml文件中配置了所有内容。
问题是即使使用它仍然会导致构建失败。这是我的cmd输出：
[INFO] ---------------------------------------------------------------------
---
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 04:43 min
[INFO] Finished at: 2016-07-12T14:22:23+02:00
[INFO] Final Memory: 11M/29M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project atlassian-bamboo-plugin-dotnet: Could not resolve dependencies for project com.atlassian.bamboo.plugins.dotnet:atlassian-bamboo-plugin-dotn
et:atlassian-plugin:5.11.2-SNAPSHOT: The following artifacts could not be resolved: com.atlassian.bamboo:atlassian-bamboo-api:jar:5.12.0-SNAPSHOT, com.atlassian.bamboo:atlassian-bam
boo-core:jar:5.12.0-SNAPSHOT, com.atlassian.bamboo.plugins.scripttask:atlassian-bamboo-plugin-scripttask:jar:5.12.0-SNAPSHOT, com.atlassian.bamboo:atlassian-bamboo-test-utils:jar:5.
12.0-SNAPSHOT: Could not find artifact com.atlassian.bamboo:atlassian-bamboo-api:jar:5.12.0-SNAPSHOT in atlassian-public (https://maven.atlassian.com/repository/public) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
之后我尝试了另外一个mvn install并得到了这个输出：
[INFO] Scanning for projects...
[WARNING] The POM for org.sonatype.plugins:nexus-staging-maven-plugin:jar:1.6.5-atlassian-2 is missing, no dependency information available
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[ERROR] Unresolveable build extension: Plugin org.sonatype.plugins:nexus-staging-maven-plugin:1.6.5-atlassian-2 or one of its dependencies could not be resolved: Failure to find org
.sonatype.plugins:nexus-staging-maven-plugin:jar:1.6.5-atlassian-2 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted unt
il the update interval of central has elapsed or updates are forced @
[ERROR] Unknown packaging: atlassian-plugin @ line 14, column 14
@
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project com.atlassian.bamboo.plugins.dotnet:atlassian-bamboo-plugin-dotnet:5.11.2-SNAPSHOT (C:\Users\Roy\Desktop\atlassian-bamboo-dotnet-plugin-7d0bf7a4f611\pom.xml) h
as 2 errors
[ERROR] Unresolveable build extension: Plugin org.sonatype.plugins:nexus-staging-maven-plugin:1.6.5-atlassian-2 or one of its dependencies could not be resolved: Failure to find
org.sonatype.plugins:nexus-staging-maven-plugin:jar:1.6.5-atlassian-2 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted
until the update interval of central has elapsed or updates are forced -> [Help 2]
[ERROR] Unknown packaging: atlassian-plugin @ line 14, column 14
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/PluginManagerException
有人可以帮我解决这个问题吗？这是pom.xml文件：
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>com.atlassian.pom</groupId>
<artifactId>public-pom</artifactId>
<version>4.0.8</version>
</parent>
<groupId>com.atlassian.bamboo.plugins.dotnet</groupId>
<artifactId>atlassian-bamboo-plugin-dotnet</artifactId>
<version>5.11.2-SNAPSHOT</version>
<packaging>atlassian-plugin</packaging>
<name>Atlassian Bamboo .NET Plugin</name>
<description>Plugin for Bamboo that provides .NET support</description>
<properties>
<bamboo.version>5.12.0-SNAPSHOT</bamboo.version>
<bamboo.data.version>5.10.0</bamboo.data.version>
<amps.version>5.0.4</amps.version>
<failOnMilestoneOrReleaseCandidateDeps>false</failOnMilestoneOrReleaseCandidateDeps>
</properties>
<scm>
<connection>scm:hg:ssh://[email protected]/atlassian/bamboo-dotnet-plugin</connection>
<developerConnection>scm:hg:ssh://[email protected]/atlassian/bamboo-dotnet-plugin</developerConnection>
<url>https://bitbucket.org/atlassian/bamboo-dotnet-plugin/src</url>
<tag>HEAD</tag>
</scm>
<issueManagement>
<system>JIRA</system>
<url>https://jira.atlassian.com/browse/BAM</url>
</issueManagement>
<licenses>
<license>
<name>BSD License</name>
<url>https://bitbucket.org/atlassian/bamboo-dotnet-plugin</url>
</license>
</licenses>
<developers>
<developer>
<name>Ross Rowe</name>
</developer>
<developer>
<name>James William Dumay</name>
<email>[email protected]</email>
</developer>
</developers>
<contributors>
<contributor>
<name>Marko Lahma</name>
</contributor>
<contributor>
<name>Krystian Brazulewicz</name>
<email>[email protected]</email>
</contributor>
<contributor>
<name>Joseph Clark</name>
<email>[email protected]</email>
</contributor>
</contributors>
<repositories>
<repository>
<id>atlassian-public</id>
<url>https://maven.atlassian.com/repository/public</url>
<snapshots>
<enabled>true</enabled>
<updatePolicy>always</updatePolicy>
<checksumPolicy>warn</checksumPolicy>
</snapshots>
<releases>
<enabled>true</enabled>
<checksumPolicy>warn</checksumPolicy>
</releases>
</repository>
</repositories>
<dependencies>
<dependency>
<groupId>com.atlassian.bamboo</groupId>
<artifactId>atlassian-bamboo-api</artifactId>
<version>${bamboo.version}</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>com.atlassian.bamboo</groupId>
<artifactId>atlassian-bamboo-core</artifactId>
<version>${bamboo.version}</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>commons-lang3</artifactId>
<version>3.4</version>
<scope>provided</scope>
</dependency>
<!-- Used for .NET script and command converters -->
<dependency>
<groupId>com.atlassian.bamboo.plugins.scripttask</groupId>
<artifactId>atlassian-bamboo-plugin-scripttask</artifactId>
<version>${bamboo.version}</version>
<scope>provided</scope>
</dependency>
<!-- Required for accessing Windows registry -->
<dependency>
<groupId>net.java.dev.jna</groupId>
<artifactId>jna-platform</artifactId>
<version>3.2.7</version>
<scope>compile</scope>
</dependency>
<!-- Test Dependencies -->
<dependency>
<groupId>com.atlassian.bamboo</groupId>
<artifactId>atlassian-bamboo-test-utils</artifactId>
<version>${bamboo.version}</version>
<scope>test</scope>
<exclusions>
<exclusion>
<groupId>com.atlassian.bamboo</groupId>
<artifactId>atlassian-bamboo-api</artifactId>
</exclusion>
<exclusion>
<groupId>com.google.collections</groupId>
<artifactId>google-collections</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.11</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>com.github.stefanbirkner</groupId>
<artifactId>system-rules</artifactId>
<version>1.5.0</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.easymock</groupId>
<artifactId>easymock</artifactId>
<version>2.4</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.easymock</groupId>
<artifactId>easymockclassextension</artifactId>
<version>2.4</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.mockito</groupId>
<artifactId>mockito-core</artifactId>
<version>1.10.19</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>pl.pragmatists</groupId>
<artifactId>JUnitParams</artifactId>
<version>1.0.2</version>
<scope>test</scope>
</dependency>
</dependencies>
<build>
<pluginManagement>
<plugins>
<plugin>
<groupId>com.atlassian.maven.plugins</groupId>
<artifactId>maven-amps-dispatcher-plugin</artifactId>
<version>${amps.version}</version>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>build-helper-maven-plugin</artifactId>
<version>1.8</version>
</plugin>
</plugins>
</pluginManagement>
<plugins>
<plugin>
<groupId>com.atlassian.maven.plugins</groupId>
<artifactId>maven-bamboo-plugin</artifactId>
<version>${amps.version}</version>
<extensions>true</extensions>
<configuration>
<productVersion>${bamboo.version}</productVersion>
<productDataVersion>${bamboo.data.version}</productDataVersion>
<extractDependencies>true</extractDependencies>
</configuration>
</plugin>
</plugins>
</build>
</project>
（这不是一个答案，但是更新，我不能适应所有原始问题，所以要保持它完整性我在这里发布）更新：
我将以下setitngs.xml文件放在我的本地.m2目录中：
<?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>
-->
<!-- The Atlassian maven plugins group used for all Atlassian Maven plugins -->
<pluginGroup>com.atlassian.maven.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>
-->
</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>
-->
<!-- Default profile containing Atlassian servers -->
<profile>
<id>defaultProfile</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<repositories>
<repository>
<id>atlassian-public</id>
<url>https://maven.atlassian.com/repository/public</url>
<snapshots>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
<checksumPolicy>warn</checksumPolicy>
</snapshots>
<releases>
<enabled>true</enabled>
<checksumPolicy>warn</checksumPolicy>
</releases>
</repository>
<repository>
<id>atlassian-plugin-sdk</id>
<url>file://${env.ATLAS_HOME}/repository</url>
<snapshots>
<enabled>true</enabled>
</snapshots>
<releases>
<enabled>true</enabled>
<checksumPolicy>warn</checksumPolicy>
</releases>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>atlassian-public</id>
<url>https://maven.atlassian.com/repository/public</url>
<releases>
<enabled>true</enabled>
<checksumPolicy>warn</checksumPolicy>
</releases>
<snapshots>
<updatePolicy>never</updatePolicy>
<checksumPolicy>warn</checksumPolicy>
</snapshots>
</pluginRepository>
<pluginRepository>
<id>atlassian-plugin-sdk</id>
<url>file://${env.ATLAS_HOME}/repository</url>
<releases>
<enabled>true</enabled>
<checksumPolicy>warn</checksumPolicy>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</pluginRepository>
</pluginRepositories>
<properties>
<downloadSources>true</downloadSources>
<downloadJavadocs>true</downloadJavadocs>
</properties>
</profile>
</profiles>
<!-- activeProfiles
| List of profiles that are active for all builds.
|
<activeProfiles>
<activeProfile>alwaysActiveProfile</activeProfile>
<activeProfile>anotherAlwaysActiveProfile</activeProfile>
</activeProfiles>
-->
</settings>
这是Atlassian SDK的settings.xml文件。我能够以这种方式下载nexus-staging-maven-plugin:jar:1.6.5-atlassian-2包。在此之后，我在清除本地mvn install目录后运行.m2\repository\com\atlassian\bamboo，因为这些包的错误，所以我再次运行mvn install并且maven抛出以下错误：
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 12.857 s
[INFO] Finished at: 2016-07-12T15:27:13+03:00
[INFO] Final Memory: 14M/34M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project atlassian-bamboo-plugin-dotnet: Could not resolve dependencies for project com.atlassian.bamboo.plugins.dotnet:atlassian-bamboo-plugin-dotnet:atlassian-plugin:5.11.2-SNAPSHOT: The following artifacts could not be resolved: com.atlassian.bamboo:atlassian-bamboo-api:jar:5.12.0-SNAPSHOT, com.atlassian.bamboo:atlassian-bamboo-core:jar:5.12.0-SNAPSHOT, com.atlassian.bamboo.plugins.scripttask:atlassian-bamboo-plugin-scripttask:jar:5.12.0-SNAPSHOT, com.atlassian.bamboo:atlassian-bamboo-test-utils:jar:5.12.0-SNAPSHOT: Could not find artifact com.atlassian.bamboo:atlassian-bamboo-api:jar:5.12.0-SNAPSHOT in atlassian-public (https://maven.atlassian.com/repository/public) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project atlassian-bamboo-plugin-dotnet: Could not resolve dependencies for project com.atlassian.bamboo.plugins.dotnet:atlassian-bamboo-plugin-dotnet:atlassian-plugin:5.11.2-SNAPSHOT: The following artifacts could not be resolved: com.atlassian.bamboo:atlassian-bamboo-api:jar:5.12.0-SNAPSHOT, com.atlassian.bamboo:atlassian-bamboo-core:jar:5.12.0-SNAPSHOT, com.atlassian.bamboo.plugins.scripttask:atlassian-bamboo-plugin-scripttask:jar:5.12.0-SNAPSHOT, com.atlassian.bamboo:atlassian-bamboo-test-utils:jar:5.12.0-SNAPSHOT: Could not find artifact com.atlassian.bamboo:atlassian-bamboo-api:jar:5.12.0-SNAPSHOT in atlassian-public (https://maven.atlassian.com/repository/public)
at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:221)
at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:127)
at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:245)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.project.DependencyResolutionException: Could not resolve dependencies for project com.atlassian.bamboo.plugins.dotnet:atlassian-bamboo-plugin-dotnet:atlassian-plugin:5.11.2-SNAPSHOT: The following artifacts could not be resolved: com.atlassian.bamboo:atlassian-bamboo-api:jar:5.12.0-SNAPSHOT, com.atlassian.bamboo:atlassian-bamboo-core:jar:5.12.0-SNAPSHOT, com.atlassian.bamboo.plugins.scripttask:atlassian-bamboo-plugin-scripttask:jar:5.12.0-SNAPSHOT, com.atlassian.bamboo:atlassian-bamboo-test-utils:jar:5.12.0-SNAPSHOT: Could not find artifact com.atlassian.bamboo:atlassian-bamboo-api:jar:5.12.0-SNAPSHOT in atlassian-public (https://maven.atlassian.com/repository/public)
at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:211)
at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:195)
... 23 more
Caused by: org.eclipse.aether.resolution.DependencyResolutionException: The following artifacts could not be resolved: com.atlassian.bamboo:atlassian-bamboo-api:jar:5.12.0-SNAPSHOT, com.atlassian.bamboo:atlassian-bamboo-core:jar:5.12.0-SNAPSHOT, com.atlassian.bamboo.plugins.scripttask:atlassian-bamboo-plugin-scripttask:jar:5.12.0-SNAPSHOT, com.atlassian.bamboo:atlassian-bamboo-test-utils:jar:5.12.0-SNAPSHOT: Could not find artifact com.atlassian.bamboo:atlassian-bamboo-api:jar:5.12.0-SNAPSHOT in atlassian-public (https://maven.atlassian.com/repository/public)
at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:384)
at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:205)
... 24 more
Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: The following artifacts could not be resolved: com.atlassian.bamboo:atlassian-bamboo-api:jar:5.12.0-SNAPSHOT, com.atlassian.bamboo:atlassian-bamboo-core:jar:5.12.0-SNAPSHOT, com.atlassian.bamboo.plugins.scripttask:atlassian-bamboo-plugin-scripttask:jar:5.12.0-SNAPSHOT, com.atlassian.bamboo:atlassian-bamboo-test-utils:jar:5.12.0-SNAPSHOT: Could not find artifact com.atlassian.bamboo:atlassian-bamboo-api:jar:5.12.0-SNAPSHOT in atlassian-public (https://maven.atlassian.com/repository/public)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)
at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:367)
... 25 more
Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find artifact com.atlassian.bamboo:atlassian-bamboo-api:jar:5.12.0-SNAPSHOT in atlassian-public (https://maven.atlassian.com/repository/public)
at org.eclipse.aether.connector.basic.ArtifactTransportListener.transferFailed(ArtifactTransportListener.java:39)
at org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:355)
at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
所以我解决了。 问题是在Atlassian存储库中没有这样的版本5.11.12-SNAPSHOT版本所以我只是用最新版本替换了版本。我不知道它是否会导致更新的依赖版本的兼容性问题，但更改它解决了依赖项下载问题。