2014-04-23 19:34 GMT+02:00 Jörg Hohwiller <jo...@j-hohwiller.de>: > 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.
IIRC, PGP isn't used at all for credentials, only for signing artifacts (only enabled through a profile during relelase). You don't have to specify anything as a parameter on the CLI, everything about it is done inside your settings.xml. Using the settings.xml template in the link above, and replacing with your codehaus credentials (which you want to double-check using it to log into nexus Codehaus for example). About validating pgp behaviour, use "mvn clean verify site -Pmojo-release" (see http://mojo.codehaus.org/development/performing-a-release.html#Releasing_the_Mojo_Parent_POM ). > >> 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 > and removes this from the output after it is completed. Then it uploads > the next artifact: > 8/8 B > only afterwards the BUILD ERROR and 401 shows up. > > >> 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> > This is indeed the scm of the parent. But your is already correct now IIRC, Robert fixed it. > And modules are not inside the parents folder so there is no other way. > Got it. > >> >> Cheers >> > Thanks for your hints. > > Regards > Jörg > > -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
