When I had whacky problems with my SVN client, I upgraded to 1.6. It's worth a shot if you haven't.
Paul On Sun, Nov 29, 2009 at 1:52 PM, gerhard preisinger <[email protected]> wrote: > Hello Paul, > I am quite sure I did it from the 'root' directory, but just to be sure i > did a rerun again with following command: > > slartibartf...@baerlauch:~/Development/workspaces/spring/tagging/root$ mvn > release:clean release:prepare > > and got the same exception again. > > [INFO] > ------------------------------------------------------------------------ > [ERROR] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Unable to commit files > Provider message: > The svn command failed. > Command output: > svn: '/home/slartibartfast/Development/workspaces/spring/tagging' is not a > working copy > svn: Can't open file > '/home/slartibartfast/Development/workspaces/spring/tagging/.svn/entries': > No such file or directory > > Also I verified that there is no svn metadata in the tagging folder: > > slartibartf...@baerlauch:~/Development/workspaces/spring/tagging$ ls -l -a > total 24 > drwxr-xr-x 6 slartibartfast slartibartfast 4096 2009-11-26 23:23 . > drwxr-xr-x 18 slartibartfast slartibartfast 4096 2009-11-26 22:58 .. > drwxr-xr-x 5 slartibartfast slartibartfast 4096 2009-11-29 20:41 child1 > drwxr-xr-x 5 slartibartfast slartibartfast 4096 2009-11-29 20:41 child2 > drwxr-xr-x 5 slartibartfast slartibartfast 4096 2009-11-29 20:41 child3 > drwxr-xr-x 3 slartibartfast slartibartfast 4096 2009-11-29 20:41 root > slartibartf...@baerlauch:~/Development/workspaces/spring/tagging$ > > Do you have any other ideas? Thanks. > Gerhard > > > Paul Benedict wrote: >> >> Gerhard, >> >> It does not look like you're actually building in the root directory, >> but the tagging directory. The error message shows commit activity is >> trying to occur inside the tagging directory. >> >> >>> >>> Command output: >>> svn: '/home/slartibartfast/Development/workspaces/spring/tagging' is not >>> a working copy >>> svn: Can't open file >>> >>> >>> '/home/slartibartfast/Development/workspaces/spring/tagging/.svn/entries': >>> No such file or directory >>> >> >> The commands should be something like: >> cd /home/slartibartfast/Development/workspaces/spring/tagging/root >> mvn release:prepare >> >> But what I am more concerned about is how you say the "tagging" >> directory is *not* in SVN, yet the error message clearly shows there's >> SVN metadata in the folder. >> >> Paul >> >> On Sun, Nov 29, 2009 at 1:27 PM, gerhard preisinger >> <[email protected]> wrote: >> >>> >>> Thanks for your fast response. This actually is actually my layout, >>> though >>> my email client must have messed with the formatting of the tree. As you >>> said i started the release at root and this is where i got the error. >>> What >>> you have labeled with '(your local project)' is an ordinary folder with >>> no >>> svn metadata. >>> Gerhard >>> >>> Paul Benedict wrote: >>> >>>> >>>> I think your project structure is incorrect. I believe it should be this >>>> instead: >>>> >>>> -tagging (your local project) >>>> |-- root >>>> | |-- .svn >>>> | |-- pom.xml (parent pom) >>>> |-- child1 >>>> | |-- .svn >>>> | |-- pom.xml >>>> |-- child2 >>>> | |-- .svn >>>> | |-- pom.xml >>>> |-- child3 >>>> | |-- .svn >>>> | |-- pom.xml >>>> >>>> Perform the release starting at root. Because the childX projects are >>>> modules of root, those will be released at the same time. >>>> >>>> Paul >>>> >>>> On 11/29/2009 12:31 PM, gerhard preisinger wrote: >>>> >>>>> >>>>> Hi all, >>>>> does the release plugin expect any special organisation of code in svn? >>>>> i have mutliproject which looks like this: >>>>> >>>>> -tagging (note, this parent folder is not under version control) >>>>> |- root >>>>> |-.svn >>>>> |-pom.xml (parent pom) >>>>> |- child1 >>>>> |-.svn >>>>> |-pom.xml >>>>> |- child2 >>>>> |-.svn >>>>> |-pom.xml >>>>> |- child3 >>>>> |-.svn >>>>> |-pom.xml >>>>> >>>>> with an subversion structure like this: >>>>> >>>>> |-tagging >>>>> |-root >>>>> |-branches >>>>> |-tags >>>>> |-trunk (<-- this is checked out into folder 'tagging') >>>>> |- pom.xml >>>>> |-child1 >>>>> |-branches >>>>> |-tags >>>>> |-trunk (<-- this is checked out into folder 'tagging') >>>>> |- pom.xml >>>>> |-child2 >>>>> |-branches >>>>> |-tags >>>>> |-trunk (<-- this is checked out into folder 'tagging') >>>>> |- pom.xml >>>>> |-child3 >>>>> |-branches >>>>> |-tags >>>>> |-trunk (<-- this is checked out into folder 'tagging') >>>>> |- pom.xml >>>>> >>>>> when i now do a mvn release:prepare I get following exeception (this is >>>>> because the parent folder 'tagging' is not under version control) >>>>> >>>>> INFO] Checking in modified POMs... >>>>> [INFO] Executing: /bin/sh -c cd >>>>> /home/slartibartfast/Development/workspaces/spring/tagging/root && svn >>>>> --non-interactive commit --file /tmp/maven-scm-1136921401.commit >>>>> --targets /tmp/maven-scm-8710897044971377748-targets >>>>> [INFO] Working directory: >>>>> /home/slartibartfast/Development/workspaces/spring/tagging/root >>>>> [INFO] >>>>> >>>>> ------------------------------------------------------------------------ >>>>> [ERROR] BUILD FAILURE >>>>> [INFO] >>>>> >>>>> ------------------------------------------------------------------------ >>>>> [INFO] Unable to commit files >>>>> Provider message: >>>>> The svn command failed. >>>>> Command output: >>>>> svn: '/home/slartibartfast/Development/workspaces/spring/tagging' is >>>>> not >>>>> a working copy >>>>> svn: Can't open file >>>>> >>>>> >>>>> '/home/slartibartfast/Development/workspaces/spring/tagging/.svn/entries': >>>>> No such file or directory >>>>> >>>>> So my questions is: can I make this somehow work with my current >>>>> project/svn layout or would I have to make changes to it? Any Ideas? >>>>> Thanks. >>>>> Regards, >>>>> Gerhard >>>>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
