title: Maven artifact jboss-as-client broken (trove:trove:jar:2.1.1)
body: <p>I have serious problems on a new computer setting up my existing maven project. Eclipse complains dozens of times about missing artifacts:</p>
  
  <pre><code>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
  ...
  </code></pre>
  
  <p>While downloading the files for the local repository I encounter the following message (executing <code>mvn compile</code>:</p>
  
  <pre><code>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
  </code></pre>
  
  <p>I've followed the instructions <a href="http://community.jboss.org/wiki/MavenSettings" rel="noreferrer">http://community.jboss.org/wiki/MavenSettings</a> and use the public repository:</p>
  
  <pre><code>&lt;repository&gt;
     &lt;id&gt;jboss-public-repository&lt;/id&gt;
     &lt;name&gt;JBoss Repository&lt;/name&gt;
     &lt;url&gt;http://repository.jboss.org/nexus/content/groups/public-jboss/&lt;/url&gt;&gt;
  &lt;/repository&gt;
  </code></pre>
  
  <p>The responsible dependency in my project is </p>
  
  <pre><code>&lt;dependency&gt;
    &lt;groupId&gt;org.jboss.jbossas&lt;/groupId&gt;
    &lt;artifactId&gt;jboss-as-client&lt;/artifactId&gt;
    &lt;version&gt;6.0.0.Final&lt;/version&gt;
    &lt;type&gt;pom&lt;/type&gt;
  &lt;/dependency&gt;
  </code></pre>
  
  <p>It seems the problem is related to <a href="https://issues.jboss.org/browse/JBBUILD-682" rel="noreferrer">https://issues.jboss.org/browse/JBBUILD-682</a>, 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.</p>