Hi Emmanuel, As you said the dry run works, but when I try to run mvn deploy, with bellow error:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project kerby-all: Failed to deploy artifacts: Could not transfer artifact org.apache.kerby:kerby-all:pom:1.0.0-RC1-20150827.033743-1 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots): Access denied to: https://repository.apache.org/content/repositories/snapshots/org/apache/kerby/kerby-all/1.0.0-RC1-SNAPSHOT/kerby-all-1.0.0-RC1-20150827.033743-1.pom, ReasonPhrase:Forbidden. -> [Help 1] In my setting.xml: <server> <id>apache.snapshots.https</id> <username>plusplusjiajia</username> <password>*****</password> </server> So I can't continue the test. Thanks Jiajia -----Original Message----- From: Li, Jiajia [mailto:[email protected]] Sent: Wednesday, August 26, 2015 2:42 PM To: [email protected] Subject: RE: Release preparation Thanks for Emmanuel pointing out the step with issue. -----Original Message----- From: Emmanuel Lécharny [mailto:[email protected]] Sent: Wednesday, August 26, 2015 3:37 AM To: [email protected] Subject: Re: Release preparation Le 25/08/15 20:31, Stefan Seelmann a écrit : > On 08/25/2015 03:04 PM, Li, Jiajia wrote: >> I've removed some plugins declaration in the pom, because I don't know to >> how check whether it is ok for cutting the release, so can you take some >> time to check? > Hi Jiajia, > > you can test the release build by running the "dryRun". This shows at > least if the release build works. > > You need a GPG key, for the "dryRun" you can use any but for a real > release a strong one is required [3]. > > You should also prepare your Maven settings.xml, [1] shows an example. > > Then run the dryRun release build with > > mvn release:prepare -DdryRun=true -B FTR, the dry run works. It's when I tried a mvn deploy that I had issue last week-end.
