Renaming a Java package in SVN is circular nightmare of Out of Date, and Does not Exist errors

Question

I am trying to rename a Java package that is tracked in SVN. It all seems to work. It moves the code to the new package, etc. However, that's when the nightmare begins, the fun starts depending on your perspective. Getting rid of the old package is hard.

I get into a circular war of "out of date" or "does not exist" messages.

I try delete, cleanup, synchronize, override and commit, update, override and update, everything damn thing I can think of to get rid of the old package.

So, my question is: apparently there is a right way and a wrong way to rename a package.

I'm using SpringSource ToolSuite, if that matters.

Every once in awhile I can get it done in 15 or 20 tries, other times, I just abandon the entire thing.

Why is renaming a package such a problem for SVN.

Have you tried svn move com\example\test test\example\com? — Andrew Logvinov
– Andrew Logvinov, Commented Jul 23, 2012 at 14:52
Do you mean that you IDE renames a package without calling "svn move" and everything is ok from Java perspective, but you want SVN to understand that the files are moved? — Dmitry Pavlenko
– Dmitry Pavlenko, Commented Jul 23, 2012 at 15:24
@Andrew, I do everything in SpringSource ToolSuite IDE.... The command line is not my world — Davidson
– Davidson, Commented Jul 23, 2012 at 16:52
@Dmitry. Yes.. Java moves are correct. SVN just skids when I try to rename a package. I've learned that! The new package is out-of-date (grrr) and won't commit, and the old package has synchronized conflicts that I can't get past. Override and Commit/Update are just rocks I throw to see is something will work. Sometimes they do, sometimes they don't. Deleting the old package is also an exercise in futility. When it comes to handling packages, SVN seems to be easily foo-barred. — Davidson
– Davidson, Commented Jul 23, 2012 at 17:01
Do you have an SVN plugin installed? I prefer subversive. It is available from the STS extensions page on the dashboard. — Andrew Eisenberg
– Andrew Eisenberg, Commented Jul 24, 2012 at 19:39

ken411 · Accepted Answer · 2017-10-11 14:49:16Z

1

I know this is an old post, but I just ran into it again myself recently. I ended up creating an entirely new package and moved my classes from the old package to the new package. I was then able to commit that new package and the moved classes. After that, I had to delete the old package at the bottom level, i.e. com.xyz.foo.bar where bar is the bottom level, and then I was finally able to commit to SVN, starting with the bottom level first. This was using Eclipse Mars and subversion team provider 1.10. Absolutely painful process.

answered Oct 11, 2017 at 14:49

ken411

214 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Renaming a Java package in SVN is circular nightmare of Out of Date, and Does not Exist errors

1 Answer 1

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Your Answer

Sign up or log in

Post as a guest

Related