SVN does not store the username in the working copy. Unless a username is explicitly specified in an SVN command, SVN uses the last cached credentials for the given repository (usually stored under $HOME/.subversion/auth on Unix).
After checking out Project1 as user2, the last-cached credentials are those of user2, so if you then perform a lock, it uses user2 regardless of the working copy. Niklas On Wed 2018-04-04 at 19:54h, Leo Donahue wrote on netcat: > Hi, > > I have been testing the Lock Feature test suite and noticed some things > about the IDE and I'm not sure whether these things contribute to my test > cases failing. > > The setup for Lock Features say: > Checkout a Java project using subversion (Project 1) > Checkout the same Java project using subversion again into a different > directory (Project 2) > Two different working copies of the same project should be opened in IDE. > > The setup does not indicate whether the same project should be checked out > using different subversion user accounts. > > I checked out the same subversion project using different user accounts > into different workspaces. > > Project1 was checked out initially as "user1" > Project1 was checked out a second time as "user2" > > When I lock a file in Project1 that was checked out as "user1", the > subversion tab says it is locked by "user2". > > Is that right? It should be locked by "user1". --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
