RE: [M2Release] MAVEN RELEASE - SVN 403 Forbidden

2013-04-30 Thread James Nord (jnord)
. /James From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Angelo Scaldaferri Sent: 30 April 2013 13:12 To: jenkinsci-users@googlegroups.com Subject: Re: [M2Release] MAVEN RELEASE - SVN 403 Forbidden I understand what you mean, but in my configurati

Re: [M2Release] MAVEN RELEASE - SVN 403 Forbidden

2013-04-30 Thread Angelo Scaldaferri
I understand what you mean, but in my configuration I've already specified the user and password that have to be passed to the maven release plugin, in fact these are visible in the log file, as you can see: [LOG] Executing Maven: -B -f /opt/...thepath.../pom.xml -DdevelopmentVersion=1.2.31-SN

[M2Release] MAVEN RELEASE - SVN 403 Forbidden

2013-04-29 Thread teilo
The release process will use the authentication available to the subversion command line client when run as the user that Jenkins runs as on the slave. If you have not told the release plugin otherwise it won't pass a user to the svn client either, so if Jenkins is running as root it will try an

[M2Release] MAVEN RELEASE - SVN 403 Forbidden

2013-04-29 Thread ascaldaferri
kins.361315.n4.nabble.com/M2Release-MAVEN-RELEASE-SVN-403-Forbidden-tp4664583.html Sent from the Jenkins users mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop rece