[jbosstools-issues] [JBoss JIRA] (JBIDE-23390) fix staging repo id for pushing releases to jboss nexus
Nick Boldt (JIRA)
issues at jboss.org
Thu Oct 20 11:22:00 EDT 2016
Nick Boldt created JBIDE-23390:
----------------------------------
Summary: fix staging repo id for pushing releases to jboss nexus
Key: JBIDE-23390
URL: https://issues.jboss.org/browse/JBIDE-23390
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, maven, target-platform
Affects Versions: 4.4.2.AM2
Reporter: Nick Boldt
Last night when trying to release jbosstools-maven-plugins I was given this error:
{code}
ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy
(default-deploy) on project tycho-plugins: Failed to deploy artifacts:
Could not transfer artifact org.jboss.tools:tycho-plugins:pom:0.26.0
from/to jboss-staging-repository
(https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/):
Failed to transfer file:
https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/org/jboss/tools/tycho-plugins/0.26.0/tycho-plugins-0.26.0.pom.
Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1]{code}
Turns out the solution is this change:
https://github.com/jbosstools/jbosstools-maven-plugins/commit/31662dca8a60297744e518a640640df7df53fc38
So, we should roll this out to the parent pom, target platforms root pom, and jbosstools-build-ci too.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jbosstools-issues
mailing list