[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: problem with S status java classes

From: Ryan Schmidt <subversion-2009a_at_ryandesign.com>
Date: Tue, 27 Jan 2009 20:56:44 -0600

On Jan 18, 2009, at 09:26, Joel Nylund wrote:

> I have an ongoing problem with my svn repository, It has mainly to do
> with java class files
> It seems somehow the class files think they are in the repository even
> though they are not, when we try to delete these class files, the
> sources get deleted also. I couldnt figure this out, but now I noticed
> that the classes folder is a status of "S".
> so for example before I build it looks like this:
> ~ Happier/WebRoot/WEB-INF/classes
> after I build it looks like:
> S Happier/WebRoot/WEB-INF/classes
> ? WebRoot/WEB-INF/classes/com/happier/goodday/actions/
> GraphController.class
> ! WebRoot/WEB-INF/classes/com/happier/goodday/actions/
> GraphController.java
> I get lots of these.
> Now when I browse the repository it doesnt even show the classes
> folder in the repository.
> But when I do an update after building, I get:
> Restored 'WebRoot/WEB-INF/classes/com/happier/goodday/actions/
> GraphController.java'
> Its like somehow svn thinks my classes folder is my source folder...
> ugh, this is a mess, please please help me figure it out, I have been
> using svn for 2 years with ruby with no problems, but with java its
> been one nightmare after another.

Subversion does not distinguish file types in this manner; it is
likely a coincidence that you are seeing problems with Java files

The "S" means that the directory is "S"witched to a different URL.
Find out what URL with "svn info" on that directory. Perhaps your
classes directory has been inadvertently switched to your source

You can "svn switch" it back to where it's supposed to be, or if you
can't work it out, just check out a new working copy from the
repository, and manually move over any changed *files* from your old
working copy that you want to keep, and that should fix it too.

Do not move *directories* over from your old working copy, as working
copy directories contain a .svn directory with administrative
information that allows Subversion to know what part of the
repository it's linked to. Since that's what's not right in your
case, you don't want to possibly copy the problem from the old
working copy to the new one.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-28 06:05:18 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.