[INFRA-4482] Why is my upload to mvn spread across multiple repositories?

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: Initial Clearing
• Component/s: Nexus
• Assignee: Brian Fox
• Reporter: stack
• Created: 23/Feb/12 19:20
• Updated: 02/Feb/14 18:55
• Resolved: 26/Mar/12 20:20

Description

I'm been struggling publishing a release to repository.apache.org. Its worked for me in the past. If you look at https://repository.apache.org/index.html#stagingRepositories (you need to be logged in), you will see that I somehow made twelve repositories when I did my mvn release:perform, each artifact element to its own repo. Any idea how that happens? (I'll attach a png that shows similar). How do I prevent it?

I have another issue where the upload to apache will fail with a 400 Bad Request very frequently uploading one of my artifact items -- usually maven-metadata.xml -- but then, just now, it went through fine. Pointers appreciated on this little nugget too.

I'm using mvn 3.0.4 and 2.2.2 of the maven:release plugin. Otherwise, my settings.xml is one that has worked for me in the past:

{code}
  <servers>
    <!-- To publish a snapshot of some part of Maven -->
    <server>
      <id>apache.snapshots.https</id>
      <username>stack
      </username>
      <password>XXXX
      </password>
    </server>
    <!-- To publish a website using Maven -->
    <!-- To stage a release of some part of Maven -->
    <server>
      <id>apache.releases.https</id>
      <username>stack
      </username>
      <password>XXXX
      </password>
    </server>
  </servers>
  <profiles>
    <profile>
      <id>apache-release</id>
      <properties>
    <gpg.keyname>00A5F21E</gpg.keyname>
    <gpg.passphrase>XXXX
    </gpg.passphrase>
      </properties>
    </profile>
  </profiles>
</settings>
{code}

My pom is here: http://svn.apache.org/viewvc/hbase/tags/0.92.0mvn/pom.xml?view=markup

Thanks for any pointers.