Re: [jboss-dev] mvn release failure

I am now running into this same/similar issue. I am trying to release an alpha of jboss-javaee-parent (and jboss-ejb-api) from here http://anonsvn.jboss.org/repos/jbossas/projects/javaee/trunk/build/pom.xml and Maven keeps ending up with this error: [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /NotBackedUp/jpai/business/jboss/wc/jbossas/projects/javaee/trunk/build && svn --non-interactive commit --file /tmp/maven-scm-1338528099.commit --targets /tmp/maven-scm-4040308354544893059-targets [INFO] Working directory: /NotBackedUp/jpai/business/jboss/wc/jbossas/projects/javaee/trunk/build [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Unable to commit files Provider message: The svn command failed. Command output: svn: Commit failed (details follow): svn: Server sent unexpected return value (403 Forbidden) in response to MKACTIVITY request for '/repos/jbossas/!svn/act/e077bcbf-4cf0-4164-a657-db87cd13cfcd' Infact, i can't even do a "mvn clean deploy" to deploy a SNAPSHOT of this project. The one common thing about all these failing projects (including the one Flavia mentioned) is that they all use 5-beta-5 version of jboss-parent. <parent> <groupId>org.jboss</groupId> <artifactId>jboss-parent</artifactId> <version>5-beta-5</version> </parent> And looking at that pom http://repository.jboss.org/maven2/org/jboss/jboss-parent/5-beta-5/jboss-... i see that there have been major changes to the distributionManagement section since jboss-parent-4/jboss-parent-5-beta-1: <distributionManagement> <repository> <id>jboss-releases</id> <name>JBoss Release Repository</name> <url>${jboss.releases.repo.url}</url> </repository> <snapshotRepository> <id>jboss-snapshots</id> <name>JBoss Snapshot Repository</name> <url>${jboss.snapshots.repo.url}</url> </snapshotRepository> </distributionManagement> It now uses 2 different ids "jboss-releases" and "jboss-snapshots" for the distribution management repositories. Earlier, it was "repository.jboss.org" and "snapshots.jboss.org". That explains why my snapshot deploy failed - it couldn't find a corresponding server for username/password in settings.xml. I had to add this in settings.xml to get the SNAPSHOT deploy working. <server> <!-- Configuration of the webdav access to the snapshots repository --> <id>jboss-snapshots</id> <username>myusername</username> <password>mypass</password> </server> Looks like Paul has updated the MavenSettingsExample[1] wiki to reflect this change. However, this doesn't explain why the tagging during release is failing. I do see another change in the "jboss-releases" distribution management repository config for jboss-parent-5-beta-5: <distributionManagement> <repository> <id>jboss-releases</id> <name>JBoss Release Repository</name> <url>${jboss.releases.repo.url}</url> </repository> and the ${jboss.releases.repo.url} points to: <jboss.releases.repo.url>scm:svn:https://svn.jboss.org/repos/repository... In the earlier versions, this used to point to the local checkout of the maven repo: <distributionManagement> <repository> <!-- Copy the distribution jar file to a local checkout of the maven repository - This variable can be set in $MAVEN_HOME/conf/settings.xml --> <id>repository.jboss.org</id> <url>file://${maven.repository.root}</url> </repository> Not sure if this is causing the release issues. Maybe Paul knows? [1] http://community.jboss.org/wiki/MavenSettingsExample Flavia Rainone wrote: