You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Karl Heinz Marbaise (JIRA)" <ji...@apache.org> on 2014/09/10 20:03:34 UTC

[jira] [Commented] (INFRA-8334) Unable to deploy to Nexus since recent upgrade

    [ https://issues.apache.org/jira/browse/INFRA-8334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14128818#comment-14128818 ] 

Karl Heinz Marbaise commented on INFRA-8334:
--------------------------------------------

Unfortunately i have to acknowledge this for the area of a maven component. Currently I'm trying to deploy a component under org/apache/maven/shared which fails with the following:
{code}
[INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy (default-deploy) on project maven-dependency-analyzer: Failed to deploy artifacts: Could not transfer artifact org.apache.maven.shared:maven-dependency-analyzer:jar:1.5 from/to apache.releases.https (https://repository.apache.org/service/local/staging/deploy/maven2): Access denied to: https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/maven/shared/maven-dependency-analyzer/1.5/maven-dependency-analyzer-1.5.jar, ReasonPhrase: Forbidden. -> [Help 1]
{code}
A few days ago i have released a plugin which worked...and could be found here: https://repository.apache.org/content/repositories/maven-1053/
but i can't find the staging repositories anymore so i would not be able to release the staged repository to distribute to central.

Kind regards
Karl-Heinz Marbaise

> Unable to deploy to Nexus since recent upgrade
> ----------------------------------------------
>
>                 Key: INFRA-8334
>                 URL: https://issues.apache.org/jira/browse/INFRA-8334
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Nexus
>            Reporter: Howard M. Lewis Ship
>            Priority: Blocker
>
> I've noticed that Nexus was upgraded ... but although I can log into the web console, my Tapestry builds can no longer deploy:
> Publishing configuration: configuration ':plastic:published'
> Publishing to org.gradle.api.publication.maven.internal.ant.DefaultGroovyMavenDeployer@1117a1f6
> [ant:null] Deploying to https://repository.apache.org/service/local/staging/deploy/maven2/
> Uploading: org/apache/tapestry/plastic/5.4-beta-21/plastic-5.4-beta-21.jar to repository remote at https://repository.apache.org/service/local/staging/deploy/maven2/
> Transferring 569K from remote
> [ant:null] An error has occurred while processing the Maven artifact tasks.
>  Diagnosis:
> Error deploying artifact 'org.apache.tapestry:plastic:jar': Error deploying artifact: Authorization failed: Access denied to: https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tapestry/plastic/5.4-beta-21/plastic-5.4-beta-21.jar
> :plastic:uploadPublished FAILED
> :plastic:uploadPublished (Thread[main,5,main]) completed. Took 17.17 secs.
> FAILURE: Build failed with an exception.
> * What went wrong:
> Execution failed for task ':plastic:uploadPublished'.
> > Could not publish configuration 'published'
>    > Error deploying artifact 'org.apache.tapestry:plastic:jar': Error deploying artifact: Authorization failed: Access denied to: https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tapestry/plastic/5.4-beta-21/plastic-5.4-beta-21.jar
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --debug option to get more log output.
> BUILD FAILED
> Total time: 38.061 secs
> ~/workspaces/t5
> $
> I can't find any details on apache.org or sonatype.com about the upgrade; i.e., what I need to change in my build/configuration to continue to operate. Any pointers?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)