0

I'm so confused about this.. I think there's something missing in the error that could help, but I'm not sure.

When trying to commit to an SVN repository, NetBeans is returning this error:

org.apache.subversion.javahl.ClientException: E155007: {0} is not a working copy

Upon reading up, I've tried several things, including Updating, Cleaning Up, and Checking out.. (checking out actually screwed things up a fair bit and duplicated my project).

But all of them, still return the error. I believe the {0} part is meant to be showing a file that isn't under version control, is that correct?

Not sure where to go from here, and I can't make any more commits. If possible, I don't want to have to just abandon, and create a new project and SVN repository from scratch.

My Netbeans SVN properties shows this: enter image description here

Lee
  • 4,187
  • 6
  • 25
  • 71
  • I don't wish to sound rude, but whoever downvoted, please leave a comment as to why.. it would be really helpful! – Lee Jul 05 '16 at 13:11
  • What does NetBeans say about your svn settings (Team > Versioning Info)? – Blubberguy22 Jul 05 '16 at 13:58
  • As far as I can tell they all seem correct and normal. What should I be looking for specifically? – Lee Jul 05 '16 at 14:04
  • I'm not really sure, but it might be a general svn problem, not just NetBeans (see http://stackoverflow.com/questions/374313/svn-error-not-a-working-copy). – Blubberguy22 Jul 05 '16 at 14:11
  • I really wish people would comment when downvoting. It should be compulsory. – Lee Jul 05 '16 at 16:09

2 Answers2

0

This is a problem with NetBeans that somehow it tries to run SVN commands against something that is not a Subversion working copy. All Subversion commands have to be run against repository URLs or against local working copy. NetBeans in your case somehow lost the connection with the working copy. {0} in the error clearly indicates that something is wrong with NetBeans, it does not pass path to your working copy.

If you run svn commit -m "Commit Message" when in the working copy, the commit should work fine without any errors.

I'd suggest reporting this problem to someone at NetBeans since this looks like a bug. As a workaround commit through CLI and checkout a new & clean working copy of your project to a new location and make sure that the commit and other commands work with it without any problems.

bahrep
  • 29,961
  • 12
  • 103
  • 150
  • Thanks for that. How do I commit via CLI in NetBeans? – Lee Jul 06 '16 at 10:45
  • @Lee CLI means command-line interface implying that you should run `svn commit` in the command prompt, not in NetBeans IDE. – bahrep Jul 06 '16 at 13:17
  • I know what CLI means, but the way you were explaining, I thought there was a feature inside NetBeans to do this. Can I run SVN commands directly in the CMD prompt then? – Lee Jul 06 '16 at 13:22
  • @lee yes. Just make sure that you actually have `svn` client properly installed. – bahrep Jul 06 '16 at 13:55
0

I ran into this when my project wasn't set up correctly on the SVN server. Make sure to check-out your project, merge as needed, THEN commit.

user8947287
  • 1