Re: [mojo-dev] Release process - release:prepare not working

[Jörg Hohwiller]

Hi Mathus,

thanks for your response.

Am 22.04.2014 22:28, schrieb Baptiste Mathus:

Did you succeed with a simple 'mvn deploy' of a snapshot as I said previously? That would prevent you from trying to release by first getting the auth right with a simpler process than a release one. Because deploying a snapshot already requires you get credentials config right (though the pgp part is something else, IIRC).

Indeed "mvn deploy" fails as well. It does not even ask me for PGP passphrase. So how does the authentication work.

Obviously I missing something and after double-checking I found it:
http://mojo.codehaus.org/development/performing-a-release.html#Preparing_your_environment
Sorry.

From the output above, nothing got actually uploaded. Maybe I missed a line, what makes you think some parts made it through? (no line containing 'Uploaded [...]').

Maven temporary writes the progress on the console:
29/29 KB

8/8 B
only afterwards the BUILD ERROR and 401 shows up.

and removes this from the output after it is completed. Then it uploads the next artifact:

About the parent, I'm not sure I understand what you mean? The scm tag of the parent pom describes itself, and it just has to be redefined in the to-be-released mojos, is that your question?

I use a different layout and approach and in my case inheritance of SCM is working without redundancy. I thought this is the way it was meant to be by maven.

However here it is:
  <scm>
<connection>scm:svn:http://svn.codehaus.org/mojo/trunk/mojo/mojo-parent</connection>
<developerConnection>scm:svn:https://svn.codehaus.org/mojo/trunk/mojo/mojo-parent</developerConnection>
<url>http://fisheye.codehaus.org/browse/mojo/trunk/mojo/mojo-parent</url>
  </scm>
And modules are not inside the parents folder so there is no other way.
Got it.

Cheers

Thanks for your hints.

Regards
  Jörg

smime.p7s
Description: S/MIME Cryptographic Signature