Hi Ken,
I don't know what is causing this issue, however, I always use -X -e flags when I execute mvn. The first one produces debug output and the latter displays error messages. Just my two cents :) HTH, Bruno P. Kinoshita http://kinoshita.eti.br http://tupilabs.com ________________________________ De: Ken Gilmer <kgil...@gmail.com> Para: dev@felix.apache.org Enviadas: Terça-feira, 29 de Novembro de 2011 7:29 Assunto: svn tag failure during release:prepare Hi, I'm going for attempt #2 to release the httplite bundle. I have upgraded the parent pom version in the local pom.xml. In following the release procedure everything looks alright until I get to the 'mvn release:prepare' step which fails with: [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /home/kgilmer/dev/repos/felix-trunk/httplite && svn --non-interactive commit --file /tmp/maven-scm-1280215403.commit --targets /tmp/maven-scm-4132652216088199281-targets [INFO] Working directory: /home/kgilmer/dev/repos/felix-trunk/httplite [INFO] Tagging release with the label org.apache.felix.httplite-0.1.2... [INFO] Executing: /bin/sh -c cd /home/kgilmer/dev/repos/felix-trunk/httplite && svn --non-interactive copy --file /tmp/maven-scm-899510912.commit --revision 1207801 https://svn.apache.org/repos/asf/felix/releases/felix-parent-2.1/org.apache.felix.httplite https://svn.apache.org/repos/asf/felix/releases/org.apache.felix.httplite-0.1.2 [INFO] Working directory: /home/kgilmer/dev/repos/felix-trunk/httplite [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Path ' https://svn.apache.org/repos/asf/felix/releases/felix-parent-2.1/org.apache.felix.httplite' does not exist in revision 1207801 It looks to me that the tag path is being incorrectly with 'felix-parent-2.1' rather than 'org.apache.felix.httplite-0.1.2', however I'm not sure what the problem with the pom is. Before upgrading the pom I did not see this issue. Any ideas? thx, ken
