I should have mentioned before, the old staging repo corresponding to this fortress-core release was dropped by me (on repository.apache.org) just a few minutes ago. I’ve and re-run the mvn release step, but the error persists.
Clearly I don’t have authorization to publish. I’m guess something changed like the gpg pubkey being associated? Please advise. —Shawn > On Jul 13, 2018, at 10:45 AM, Shawn McKinney <smckin...@symas.com> wrote: > > Hello, > > I am a PMC on the Apache Directory project and trying to release one of its > subprojects - Fortress. > > I am getting an error uploading the .jar file to the apache maven repo. The > problem occurs during this step of the release process: > > mvn -Papache-release release:perform > > with this error in the console: > > [INFO] [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on > project fortress-core: Failed to deploy artifacts: Could not transfer > artifact org.apache.directory.fortress:fortress-core:jar:2.0.1 from/to > apache.releases.https > (https://repository.apache.org/service/local/staging/deploy/maven2): Failed > to transfer file: > https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/directory/fortress/fortress-core/2.0.1/fortress-core-2.0.1.jar. > Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1] > > *** > > I just ran this process a few days ago with no problems meaning before the > authorization was there. I am running on the same machine as the same user. > > Can you help or point me in the right direction? > > Thanks > —Shawn
