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

[Subclipse-users] Bug or unexpected behavior when comitting files in non versioned folders

From: Reinhard Brandstaedter <Reinhard.Brandstaedter_at_jku.at>
Date: 2007-01-15 16:38:10 CET

Hi,

I just found something that is - in my opinion - a unexpected behavior
in subclipse.

Assume I create a new folder in my working copy and in this folder a new
file. I don't add this file or folder to version control.
Then I issue a "commit" on the file.
Subclipse then implicitly creates another transaction and commits the
parent folder, resulting in two commits with the same message.

The console output:

add -N /opt/workspace/sandbox/development/wkpkg-test4
A /opt/workspace/sandbox/development/wkpkg-test4
add -N /opt/workspace/sandbox/development/wkpkg-test4/test1.txt
A /opt/workspace/sandbox/development/wkpkg-test4/test1.txt
commit -m "Test commit file in folder that doesn't exist in repository
yet" -N /opt/workspace/sandbox/development/wkpkg-test4
Adding /opt/workspace/sandbox/development/wkpkg-test4
Committed revision 48.
commit -m "Test commit file in folder that doesn't exist in repository
yet" /opt/workspace/sandbox/development/wkpkg-test4/test1.txt

Adding /opt/workspace/sandbox/development/wkpkg-test4/test1.txt
Transmitting file data ...
Committed revision 49.

I think subclipse should either add the parent folder to the original
transaction and commit both, the file and the folder, in one commit or
issue a warning as does the SVN commandline client:

# ~/wc/sandbox/development $ mkdir wkpkg-test5
# ~/wc/sandbox/development $ cd wkpkg-test5/
# ~/wc/sandbox/development/wkpkg-test5 $ ls
# ~/wc/sandbox/development/wkpkg-test5 $ touch test1.txt
# ~/wc/sandbox/development/wkpkg-test5 $ svn commit test1.txt
svn: '/home/reinhard/wc/sandbox/development/wkpkg-test5' is not a
working copy
svn: Can't open file
'/home/reinhard/wc/sandbox/development/wkpkg-test5/.svn/entries': No
such file or directory
# ~/wc/sandbox/development/wkpkg-test5 $ cd ..
# ~/wc/sandbox/development $ svn commit wkpkg-test5/test1.txt
svn: '/home/reinhard/wc/sandbox/development/wkpkg-test5' is not a
working copy
svn: Can't open file
'/home/reinhard/wc/sandbox/development/wkpkg-test5/.svn/entries': No
such file or directory
# ~/wc/sandbox/development $ cd wkpkg-test5/
# ~/wc/sandbox/development/wkpkg-test5 $ svn add test1.txt
svn: '.' is not a working copy
svn: Can't open file '.svn/entries': No such file or directory
# ~/wc/sandbox/development/wkpkg-test5 $ cd ..
# ~/wc/sandbox/development $ svn add wkpkg-test5
A wkpkg-test5
A wkpkg-test5/test1.txt
# ~/wc/sandbox/development $ svn commit wkpkg-test5/test1.txt
svn: Commit failed (details follow):
svn: '/home/reinhard/wc/sandbox/development/wkpkg-test5' is not under
version control and is not part of the commit, yet its child
'/home/reinhard/wc/sandbox/development/wkpkg-test5/test1.txt' is part of
the commit
# ~/wc/sandbox/development $

I think this should be fixed, because from a users view committing the
file should involve committing the folder also but in only one changeset
(one revision).

btw. I checked the behavior in subversive (polarion.org plugin) and they
do it in one commit.

Reinhard

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Jan 15 17:07:27 2007

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

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