Maven artifact jboss-as-client broken(trove:trove:jar:2.1.1) [英] Maven artifact jboss-as-client broken (trove:trove:jar:2.1.1)

查看:162
本文介绍了Maven artifact jboss-as-client broken(trove:trove:jar:2.1.1)的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我在设置现有maven项目的新计算机上遇到严重问题。 Eclipse抱怨了几十次丢失的工件:

I have serious problems on a new computer setting up my existing maven project. Eclipse complains dozens of times about missing artifacts:

Missing artifact junit:junit:jar:4.8.2:test
Missing artifact org.slf4j:slf4j-log4j12:jar:1.5.5:compile
Missing artifact org.slf4j:slf4j-api:jar:1.5.5:compile
Missing artifact log4j:log4j:jar:1.2.14:compile
...

下载本地存储库的文件时我遇到以下消息(执行 mvn compile

While downloading the files for the local repository I encounter the following message (executing mvn compile:

Downloading: http://repository.jboss.org/maven2/trove/trove/2.1.1/trove-2.1.1.pom
Downloading: http://repository.jboss.org/maven2/trove/trove/2.1.1/trove-2.1.1.pom
....
[ERROR] ... Failed to read artifact descriptor for trove:trove:jar:2.1.1:
        Could not transfer artifact trove:trove:pom:2.1.1 from/to jboss 
        (http://repository.jboss.org/maven2): Access denied to:
        http://repository.jboss.org/maven2/trove/trove/2.1.1/trove-2.1.1.pom

我按照说明 http ://community.jboss.org/wiki/MavenSettings 并使用公共存储库:

I've followed the instructions http://community.jboss.org/wiki/MavenSettings and use the public repository:

<repository>
   <id>jboss-public-repository</id>
   <name>JBoss Repository</name>
   <url>http://repository.jboss.org/nexus/content/groups/public-jboss/</url>>
</repository>

我项目中的责任依赖是

<dependency>
  <groupId>org.jboss.jbossas</groupId>
  <artifactId>jboss-as-client</artifactId>
  <version>6.0.0.Final</version>
  <type>pom</type>
</dependency>

似乎问题与 https://issues.jboss.org/browse/JBBUILD-682 ,但由于存储库URL不太可能被修复,我正在寻找一个解决方法!我没有在其他机器上遇到这个问题,但是如果maven存储库被删除并且将被重建它就会发生。

It seems the problem is related to https://issues.jboss.org/browse/JBBUILD-682, but since it's unlikely the repository URL will be fixed, I'm looking for a workaround! I don't encounter this problem on other machines, but it occurs if the maven repository is deleted and will be rebuild.

推荐答案

我想我曾经有过这个问题,并且afaik知道使用不赞成的依赖关系帮助了我。

I think I had that issue once before and afaik know "Using Deprecated Dependencies" helped me.

看看 http://community.jboss.org/wiki/MavenGettingStarted-Users 关于使用不推荐使用的依赖关系的段落。对不起,我可能错了,但可能值得一试...... :)

Have a look at http://community.jboss.org/wiki/MavenGettingStarted-Users on paragraph "Using Deprecated Dependencies". Sorry I might be wrong, but it might be worth a shot... :)

Maven来源报价:

Maven Source Quote:

  <repositories>
    <!-- other repos here -->
    <repository>
      <id>jboss-deprecated-repository</id>
      <name>JBoss Deprecated Maven Repository</name>
      <url>https://repository.jboss.org/nexus/content/repositories/deprecated/</url>
      <layout>default</layout>
      <releases>
        <enabled>true</enabled>
        <updatePolicy>never</updatePolicy>
      </releases>
      <snapshots>
        <enabled>false</enabled>
        <updatePolicy>never</updatePolicy>
      </snapshots>
    </repository>
  </repositories>

这篇关于Maven artifact jboss-as-client broken(trove:trove:jar:2.1.1)的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆