hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl Steinbach (Updated) (JIRA)" <>
Subject [jira] [Updated] (HIVE-2243) Can't publish maven release artifacts to apache repository
Date Mon, 03 Oct 2011 20:39:36 GMT


Carl Steinbach updated HIVE-2243:

    Attachment: HIVE-2243.1.patch.txt
> Can't publish maven release artifacts to apache repository
> ----------------------------------------------------------
>                 Key: HIVE-2243
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Build Infrastructure
>    Affects Versions: 0.7.1
>            Reporter: Carl Steinbach
>            Assignee: Carl Steinbach
>         Attachments: HIVE-2243.1.patch.txt
> So far I haven't been able to push the maven artifacts to the Apache release repository.
Here's the error I get:
> {noformat}
> % ant maven-publish -Dmvn.publish.repo=releases
> ...
> maven-publish-artifact:
> [artifact:install-provider] Installing provider: org.apache.maven.wagon:wagon-http:jar:1.0-beta-2:runtime
> [artifact:deploy] Deploying to
> [artifact:deploy] Uploading: org/apache/hive/hive-anttasks/0.7.1/hive-anttasks-0.7.1.jar
to repository apache.releases.https at
> [artifact:deploy] Transferring 9K from apache.releases.https
> [artifact:deploy] An error has occurred while processing the Maven artifact tasks.
> [artifact:deploy]  Diagnosis:
> [artifact:deploy] 
> [artifact:deploy] Error deploying artifact 'org.apache.hive:hive-anttasks:jar': Error
deploying artifact: Authorization failed: Access denied to:
> {noformat}
> I get the same error when I try to publish to the staging repository.
> I took another look at the Apache "Publishing Maven Artifacts" guide (
and think that we're probably failing to include a couple fields that are required in the
pom files. It also looks like we should be pushing this to the staging repository as opposed
to the releases repository.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message