Hi Bram, It turns out I need to specify both -Dusername=[user] and -Dpassword=[password]. I still think it's strange to use http for the scm url, why not use https?
The release:prepare is complete now, but as you expected I can't "perform" it: INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy (default-deploy) on project org.amdatu.storage: Failed to deploy artifacts: Could not transfer artifact org.amdatu.storage:org.amdatu.storage:pom:1.0.0 from/to amdatu.releases (dav:http://repository.amdatu.org/releases): Access denied to: http://repository.amdatu.org/releases/org/amdatu/storage/org.amdatu.storage/1.0.0/org.amdatu.storage-1.0.0.pom -> [Help 1] Please bribe your sysadmin ;-) Paul On Nov 21, 2011, at 3:52 PM, Bram de Kruijff wrote: > Hi Paul, > > as discussed briefly over skype earlier the release:prepare should at > least work as you are able to svn commit and that's all you need. > Judging from the error you reported you need to make sure that > repository location as specified in the pom.scm matches you local > checkout repository location. > > My second point was that I can imagine release:perform will fail on > you because I suspect our sysadmins may not have enable writing to > repository.amdatu.org. If that is the case we can run it from inside > our network while trying to bride them into giving you these > privileges ;) > > grz > Bram > > On Wed, Oct 26, 2011 at 10:13 AM, Bram de Kruijff <[email protected]> > wrote: >> Hi Paul, >> >> 2011/10/25 Paul Bakker <[email protected]>: >>> Hi all, >>> As you might have seen from the 1001 commits I did in the past two hours, >> >> LOL :) >> >>> I'm trying to do a formal release of the first RC for amdatu-storage. >>> I assume you normally use the Maven release plugin to do so. Creating a tag >>> in subversion fails however because of insufficient permission. I believe >> >> So you can commit but not tag... that is strange right? I'm guessing >> the problem is in the maven config, not at the svn server end. >> >>> the problem is that in the pom there is the following: >>> <scm> >>> >>> >>> <connection>scm:svn:http://subversion.amdatu.org/svn/amdatu/trunk/amdatu-storage</connection> >>> <developerConnection>scm:svn:http://subversion.amdatu.org/svn/amdatu/trunk/amdatu-storage</developerConnection> >>> <url>scm:svn:http://subversion.amdatu.org/svn/amdatu/trunk/amdatu-storage</url> >>> </scm> >>> The developerConnection is http (not https) which can cause this problem. If >>> I look at other POMs however, all of them just use http urls. I did try to >>> use https, but in that case Maven gets confused because: >>> "svn: Source and dest appear not to be in the same repository (src: >>> 'https://subversion.amdatu.org/svn/amdatu/trunk/amdatu-storage'; dst: >>> 'http://subversion.amdatu.org/svn/amdatu/tags/org.amdatu.storage-1.0.0-RC1')" >>> I don't understand where the http is coming from in the destination url, >>> it's not in the pom anymore. >> >> What does your svn info URL say? I think it must match the >> developerConnection so if you change that to https in the pom you may >> need to svn switch --relocate your local checkout. >> >>> My question is basically, what do you use to release now? >> >> mvn release:prepare >> mvn release:perform >> >> But me and Ivo are on the internal GX network so that may be >> different. Eg. this weekend I noticed I could not do the >> release:perform upload to repository.amdatu.org from the outside. >> >> Check and try the svn info first. >> >> grz >> Bram >> > > _______________________________________________ > Amdatu-developers mailing list > [email protected] > http://lists.amdatu.org/mailman/listinfo/amdatu-developers _______________________________________________ Amdatu-developers mailing list [email protected] http://lists.amdatu.org/mailman/listinfo/amdatu-developers
