You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "stack (Commented) (JIRA)" <ji...@apache.org> on 2012/02/23 20:22:48 UTC
[jira] [Commented] (INFRA-4482) Why is my upload to mvn spread
across multiple repositories?
[ https://issues.apache.org/jira/browse/INFRA-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214952#comment-13214952 ]
stack commented on INFRA-4482:
------------------------------
I cannot pubish my staging repos even if I select all because each complains of missing elements. For example:
{code}
Staging ruleset evaluation on repository 'org.apache.hbase-049 (u:stack, a:38.99.102.224)' has failed.
Staging Checksum Validation
-Missing MD5: '/org/apache/hbase/hbase/0.92.0/hbase-0.92.0.jar.md5.'
Staging Signature Validation
-Missing Signature: '/org/apache/hbase/hbase/0.92.0/hbase-0.92.0.jar.asc' does not exist for 'hbase-0.92.0.jar'.
{code}
> Why is my upload to mvn spread across multiple repositories?
> ------------------------------------------------------------
>
> Key: INFRA-4482
> URL: https://issues.apache.org/jira/browse/INFRA-4482
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Reporter: stack
> Attachments: Screen Shot 2012-02-23 at 9.50.58 AM.png
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira