Thanks Bruno and Felix for your suggestions. I have tried 'svn update' and
mvn release:prepare' multiple times but continue to get a build failure. I
went back to the beginning of the release process. The build error I'm
getting now is slightly different:
[INFO] Building Apache Felix Lightweight HTTP Server
[INFO] task-segment: [release:prepare] (aggregator-style)
[INFO]
------------------------------------------------------------------------
[INFO] [release:prepare {execution: default-cli}]
[INFO] Resuming release from phase 'scm-tag'
[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-1734538187.commit
https://svn.apache.org/repos/asf/felix/releases/org.apache.felix.httplite-0.1.2
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/org.apache.felix.httplite-0.1.2'
does not exist in revision 1208948
I have looked in the repo and indeed `org.apache.felix.httplite-0.1.2` does
not exist. So, I'm assuming that there is an automated step that copies
from trunk to releases, and that is somehow failing. Any suggestions on
how to resolve this problem?
thx,
ken
On Tue, Nov 29, 2011 at 10:09 PM, Felix Meschberger <fmesc...@adobe.com>wrote:
> Hi,
>
> This is a known problem with the way the Subversion repo is replicated.
>
> Just svn update and run mvn release:prepare one more time (maybe
> repeatedly) until the things work.
>
> Regards
> Felix
>
>
> Am 29.11.2011 um 10:29 schrieb Ken Gilmer:
>
> > 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
>
>
