This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
This is the second time I am logging this problem and I seriously thinking to switch to anothetr IDE which has a proper svn support! On two different projects, I have freezed my rails gems using the rake command, got rspec and rspec_on_rails running the script/plugin and tried to commit the changes using "See the Changes" and the commit command from netbeans. In both cases, a big waste of time: 15-20% files are .... missing!!! This works fine with Eclipse + subeclipse. Which version of svn do you recommand?
Could you please verify whether all file are listed in "Commit" dialog. Only files listed there are committed into the repository. What type of project do you use? (web, j2se, ...) Both versions 1.3.x and 1.4.x of subversion are supported by the IDE. But please keep in mind that once working copy is "touched" by svn 1.4.x then switching back to 1.3.x svn client that won't be able to manage such working copy.
the only way i was able to reproduce: 1.) have a versioned project 2.) produce many external changes (i assume this is what "... freezed my rails gems using the rake command, got rspec and rspec_on_rails running the script/plugin" did) 3.) switch to ide, invoke "refresh status" on the relevant context and then commit _before_ the refresh ends - the external changes aren't reflected in the ide yet, but the commit was already processed over a subset from the really changed files. The problem here is that the commit action relies on the caching mechanism in the nb svn module which unfortunately isn't uptodate. I already mentioned it in issue #114551 - it's not guaranteed that external changes will be reflected in the IDE. This problem is covered by issue #116104 - we should see that there is a deep status refresh made on a commits context. I'll try to get this fixed in beta2. now - this never happened to me if i invoked the commit after a refresh in the VV has finished - i consider this as a quite simple workaround and more, there actually is no data loss. One more thing - i'm afraid there is more to the problem - it's not very nice that a commit from the versioning view is possible until a refresh runs over the same scope - this should be fixed.
Using command line for this kind of task. Svn is too slow anyway ... Looking fwd to GIT or MERCURIAL!