Any idea what might be wrong? Or is this just one of those "mvn release:x" random failures? --------------------------------------------------------------------- [INFO] Tagging release with the label 1.0.0.Alpha1... [INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file C:\DOCUME~1\Ales\LOCALS~1\Temp\maven-scm-578495977.commit --revision 98027 https://svn.jboss.org/repos/labs/labs/jbossbuild/jboss-parent/tags/jboss-... https://svn.jboss.org/repos/jbossas/projects/mc-ann/tags/1.0.0.Alpha1" [INFO] Working directory: C:\projects\microcontainer\mc-ann [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Repository moved permanently to 'https://svn.jboss.org/repos/'; please relocate _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

I tried clean checkout, didn't help. Dimitris Andreadis wrote: > maybe you need to relocate your checkout: > > http://svnbook.red-bean.com/en/1.1/re27.html > > Ales Justin wrote: >> Any idea what might be wrong? >> Or is this just one of those "mvn release:x" random failures? >> >> --------------------------------------------------------------------- >> >> [INFO] Tagging release with the label 1.0.0.Alpha1... >> [INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file >> C:\DOCUME~1\Ales\LOCALS~1\Temp\maven-scm-578495977.commit --revision >> 98027 >> https://svn.jboss.org/repos/labs/labs/jbossbuild/jboss-parent/tags/jboss-... >> https://svn.jboss.org/repos/jbossas/projects/mc-ann/tags/1.0.0.Alpha1" >> [INFO] Working directory: C:\projects\microcontainer\mc-ann >> [INFO] >> ------------------------------------------------------------------------ >> [ERROR] BUILD FAILURE >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Unable to tag SCM >> Provider message: >> The svn tag command failed. >> Command output: >> svn: Repository moved permanently to 'https://svn.jboss.org/repos/'; >> please relocate >> _______________________________________________ >> jboss-development mailing list >> jboss-development(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-development > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development > _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

This is the root pom: * http://anonsvn.jboss.org/repos/jbossas/projects/mc-ann/trunk/pom.xml

Heiko W.Rupp wrote: > As far as I understand this is coming from the <scm> tags within the respective root pom. > > Am 20.12.2009 um 14:00 schrieb Ales Justin: > >> I tried clean checkout, didn't help. >> >> Dimitris Andreadis wrote: >>> maybe you need to relocate your checkout: >>> >>> http://svnbook.red-bean.com/en/1.1/re27.html >>> >>> Ales Justin wrote: >>>> Any idea what might be wrong? >>>> Or is this just one of those "mvn release:x" random failures? >>>> >>>> --------------------------------------------------------------------- >>>> >>>> [INFO] Tagging release with the label 1.0.0.Alpha1... >>>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file >>>> C:\DOCUME~1\Ales\LOCALS~1\Temp\maven-scm-578495977.commit --revision >>>> 98027 >>>> https://svn.jboss.org/repos/labs/labs/jbossbuild/jboss-parent/tags/jboss-... >>>> https://svn.jboss.org/repos/jbossas/projects/mc-ann/tags/1.0.0.Alpha1" >>>> [INFO] Working directory: C:\projects\microcontainer\mc-ann >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [ERROR] BUILD FAILURE >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] Unable to tag SCM >>>> Provider message: >>>> The svn tag command failed. >>>> Command output: >>>> svn: Repository moved permanently to 'https://svn.jboss.org/repos/'; >>>> please relocate >>>> _______________________________________________ >>>> jboss-development mailing list >>>> jboss-development(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jboss-development >>> _______________________________________________ >>> jboss-development mailing list >>> jboss-development(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jboss-development >>> >> _______________________________________________ >> jboss-development mailing list >> jboss-development(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-development _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

Any idea what might be wrong? Or is this just one of those "mvn release:x" random failures? --------------------------------------------------------------------- [INFO] Tagging release with the label 1.0.0.Alpha1... [INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file C:\DOCUME~1\Ales\LOCALS~1\Temp\maven-scm-578495977.commit --revision 98027 https://svn.jboss.org/repos/labs/labs/jbossbuild/jboss-parent/tags/jboss-... https://svn.jboss.org/repos/jbossas/projects/mc-ann/tags/1.0.0.Alpha1" [INFO] Working directory: C:\projects\microcontainer\mc-ann [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Repository moved permanently to 'https://svn.jboss.org/repos/'; please relocate _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

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?

Maybe you should consider also David's simplified release process: http://community.jboss.org/wiki/DavidsMavenReleaseProcess Jaikiran Pai wrote: > Looks like the Maven release process for JBoss projects has now > changed http://community.jboss.org/wiki/MavenReleaseRepository and > now use Maven Wagon SCM > http://community.jboss.org/wiki/MavenReleaseRepository > > -Jaikiran > Jaikiran Pai wrote: >> 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? >> > > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development

I agree, just use David's release process. You can use a script or just manually update the POM versions. It's not worth the effort to try to get the release plugin working, since base on past experience there is a good chance you will end up with another problem in the next release. Jaikiran Pai wrote: > Yeah, i think David's release process is probably better. Because with > the new release process explained in > http://community.jboss.org/wiki/MavenReleaseRepository, it looks like > the release will be directly commited to SVN repo. The earlier process > used to copy it to the local file system and then we used manually > commit it. That allowed us to decide whether or not to commit the > release, if something went wrong during the release. David's release > process provides me this flexibility. > > -Jaikiran > > Dimitris Andreadis wrote: >> Maybe you should consider also David's simplified release process: >> http://community.jboss.org/wiki/DavidsMavenReleaseProcess >> >> Jaikiran Pai wrote: >>> Looks like the Maven release process for JBoss projects has now >>> changed http://community.jboss.org/wiki/MavenReleaseRepository and >>> now use Maven Wagon SCM >>> http://community.jboss.org/wiki/MavenReleaseRepository >>> >>> -Jaikiran >>> Jaikiran Pai wrote: >>>> 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? >>>> >>> _______________________________________________ >>> jboss-development mailing list >>> jboss-development(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jboss-development > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

Install Cygwin or switch to a better OS :) Sent from my iPhone On Jan 7, 2010, at 12:56, Dimitris Andreadis <dandread(a)redhat.com&gt; wrote: > I think Ales said something like how he can do this on Windoze :) > > Paul Gier wrote: >> I agree, just use David's release process. You can use a script or >> just >> manually update the POM versions. It's not worth the effort to try >> to get the >> release plugin working, since base on past experience there is a >> good chance you >> will end up with another problem in the next release. >> >> Jaikiran Pai wrote: >>> Yeah, i think David's release process is probably better. Because >>> with >>> the new release process explained in >>> http://community.jboss.org/wiki/MavenReleaseRepository, it looks >>> like >>> the release will be directly commited to SVN repo. The earlier >>> process >>> used to copy it to the local file system and then we used manually >>> commit it. That allowed us to decide whether or not to commit the >>> release, if something went wrong during the release. David's >>> release >>> process provides me this flexibility. >>> >>> -Jaikiran >>> >>> Dimitris Andreadis wrote: >>>> Maybe you should consider also David's simplified release process: >>>> http://community.jboss.org/wiki/DavidsMavenReleaseProcess >>>> >>>> Jaikiran Pai wrote: >>>>> Looks like the Maven release process for JBoss projects has now >>>>> changed http://community.jboss.org/wiki/MavenReleaseRepository >>>>> and >>>>> now use Maven Wagon SCM >>>>> http://community.jboss.org/wiki/MavenReleaseRepository >>>>> >>>>> -Jaikiran >>>>> Jaikiran Pai wrote: >>>>>> 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.jboss.org/maven2</jboss.releases.repo.url> >>>>>> >>>>>> >>>>>> 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? >>>>>> >>>>> _______________________________________________ >>>>> jboss-development mailing list >>>>> jboss-development(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/jboss-development >>> _______________________________________________ >>> jboss-development mailing list >>> jboss-development(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jboss-development >> >> _______________________________________________ >> jboss-development mailing list >> jboss-development(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-development > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

Easier said than done. ;-) I never had good experiance of Cygwin, hence I doubt it will work.

And I'm changing OS as we speak, but terrible UK weather prevents my new fancy hardware to be shipped. :-) So, more suggestions welcome. Btw, what changed that prevents my releases, as I had no problems (or very little) before. Sent from my iPod On 7.1.2010, at 20:05, jason.greene(a)redhat.com wrote: > Install Cygwin or switch to a better OS :) > > Sent from my iPhone > > On Jan 7, 2010, at 12:56, Dimitris Andreadis <dandread(a)redhat.com&gt; > wrote: > >> I think Ales said something like how he can do this on Windoze :) >> >> Paul Gier wrote: >>> I agree, just use David's release process. You can use a script or >>> just >>> manually update the POM versions. It's not worth the effort to try >>> to get the >>> release plugin working, since base on past experience there is a >>> good chance you >>> will end up with another problem in the next release. >>> >>> Jaikiran Pai wrote: >>>> Yeah, i think David's release process is probably better. Because >>>> with >>>> the new release process explained in >>>> http://community.jboss.org/wiki/MavenReleaseRepository, it looks >>>> like >>>> the release will be directly commited to SVN repo. The earlier >>>> process >>>> used to copy it to the local file system and then we used manually >>>> commit it. That allowed us to decide whether or not to commit the >>>> release, if something went wrong during the release. David's >>>> release >>>> process provides me this flexibility. >>>> >>>> -Jaikiran >>>> >>>> Dimitris Andreadis wrote: >>>>> Maybe you should consider also David's simplified release process: >>>>> http://community.jboss.org/wiki/DavidsMavenReleaseProcess >>>>> >>>>> Jaikiran Pai wrote: >>>>>> Looks like the Maven release process for JBoss projects has now >>>>>> changed http://community.jboss.org/wiki/MavenReleaseRepository >>>>>> and >>>>>> now use Maven Wagon SCM >>>>>> http://community.jboss.org/wiki/MavenReleaseRepository >>>>>> >>>>>> -Jaikiran >>>>>> Jaikiran Pai wrote: >>>>>>> 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.jboss.org/maven2</jboss.releases.repo.url> >>>>>>> >>>>>>> >>>>>>> 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? >>>>>>> >>>>>> _______________________________________________ >>>>>> jboss-development mailing list >>>>>> jboss-development(a)lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development >>>> _______________________________________________ >>>> jboss-development mailing list >>>> jboss-development(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jboss-development >>> >>> _______________________________________________ >>> jboss-development mailing list >>> jboss-development(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jboss-development >> _______________________________________________ >> jboss-development mailing list >> jboss-development(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-development > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

I don't know of anything that changed that would affect this. It seems like there are just a lot of little things that can go wrong in the communication between the release plugin and svn. Did you update your local svn client? Or maybe change the version of the release plugin that you are using? The only non-windows compatible part of David's process is the perl script to update the version. For now you can either just do the version updates manually (find and replace in eclipse?) I'll work on a platform independent Perl script to do the updates. Ales Justin wrote: > Easier said than done. ;-) > > I never had good experiance of Cygwin, hence I doubt it will work. > > And I'm changing OS as we speak, > but terrible UK weather prevents my new fancy hardware to be > shipped. :-) > > So, more suggestions welcome. > > Btw, what changed that prevents my releases, > as I had no problems (or very little) before. > > Sent from my iPod > > On 7.1.2010, at 20:05, jason.greene(a)redhat.com wrote: > >> Install Cygwin or switch to a better OS :) >> >> Sent from my iPhone >> >> On Jan 7, 2010, at 12:56, Dimitris Andreadis <dandread(a)redhat.com&gt; >> wrote: >> >>> I think Ales said something like how he can do this on Windoze :) >>> >>> Paul Gier wrote: >>>> I agree, just use David's release process. You can use a script or >>>> just >>>> manually update the POM versions. It's not worth the effort to try >>>> to get the >>>> release plugin working, since base on past experience there is a >>>> good chance you >>>> will end up with another problem in the next release. >>>> >>>> Jaikiran Pai wrote: >>>>> Yeah, i think David's release process is probably better. Because >>>>> with >>>>> the new release process explained in >>>>> http://community.jboss.org/wiki/MavenReleaseRepository, it looks >>>>> like >>>>> the release will be directly commited to SVN repo. The earlier >>>>> process >>>>> used to copy it to the local file system and then we used manually >>>>> commit it. That allowed us to decide whether or not to commit the >>>>> release, if something went wrong during the release. David's >>>>> release >>>>> process provides me this flexibility. >>>>> >>>>> -Jaikiran >>>>> >>>>> Dimitris Andreadis wrote: >>>>>> Maybe you should consider also David's simplified release process: >>>>>> http://community.jboss.org/wiki/DavidsMavenReleaseProcess >>>>>> >>>>>> Jaikiran Pai wrote: >>>>>>> Looks like the Maven release process for JBoss projects has now >>>>>>> changed http://community.jboss.org/wiki/MavenReleaseRepository >>>>>>> and >>>>>>> now use Maven Wagon SCM >>>>>>> http://community.jboss.org/wiki/MavenReleaseRepository >>>>>>> >>>>>>> -Jaikiran >>>>>>> Jaikiran Pai wrote: >>>>>>>> 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.jboss.org/maven2</jboss.releases.repo.url> >>>>>>>> >>>>>>>> >>>>>>>> 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? >>>>>>>> >>>>>>> _______________________________________________ >>>>>>> jboss-development mailing list >>>>>>> jboss-development(a)lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development >>>>> _______________________________________________ >>>>> jboss-development mailing list >>>>> jboss-development(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/jboss-development >>>> _______________________________________________ >>>> jboss-development mailing list >>>> jboss-development(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jboss-development >>> _______________________________________________ >>> jboss-development mailing list >>> jboss-development(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jboss-development >> _______________________________________________ >> jboss-development mailing list >> jboss-development(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-development > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

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: > I had a similar failure when doing the classpool release, but it was not > same error as you (can't tag it cause the message was repository does > not exist). > This is what I've done: > - I checked that I forgot to define my username and password > - During the first release try, the pom was updated and for some strange > reason, I got an error and the scm address moved from trunk to tag > (don't ask me why). I had to fix my pom then. > - downgraded the version of release plugin to 2.0-beta-8 > > Downgrading didn't work for me as the other two points were the cause of > the problem. But I found an e-mail thread on the web that mentioned that > 2.0-beta-9 has a bug and that causes maven to not be able to tag it. > That's why I gave it a try. Maybe this will solve your problem? > > On 12/19/2009 04:54 PM, Ales Justin wrote: >> Any idea what might be wrong? >> Or is this just one of those "mvn release:x" random failures? >> >> --------------------------------------------------------------------- >> >> [INFO] Tagging release with the label 1.0.0.Alpha1... >> [INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file >> C:\DOCUME~1\Ales\LOCALS~1\Temp\maven-scm-578495977.commit --revision >> 98027 >> https://svn.jboss.org/repos/labs/labs/jbossbuild/jboss-parent/tags/jboss-... >> https://svn.jboss.org/repos/jbossas/projects/mc-ann/tags/1.0.0.Alpha1" >> [INFO] Working directory: C:\projects\microcontainer\mc-ann >> [INFO] >> ------------------------------------------------------------------------ >> [ERROR] BUILD FAILURE >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Unable to tag SCM >> Provider message: >> The svn tag command failed. >> Command output: >> svn: Repository moved permanently to 'https://svn.jboss.org/repos/'; >> please relocate >> _______________________________________________ >> jboss-development mailing list >> jboss-development(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-development >> _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development