Hello Ricardo, When performing url-to-url copy events are not sent for individual files, at least native Subversion doesn't send any events. It is easy to verify: native Subversion's "event handler" is implemented in the way that it prints path for event, passed to it. When you run
svn copy <SRC_URL> <DST_URL> you don't see any paths (just to compare: svn copy <FILE_IN_WC> <FILE_IN_WC> prints the path copied, and the events are sent for it). So SVNKit behaves in the same way as native Subversion. I think native Subversion doesn't print paths copied because it is not possible in Subversion protocols. When you run copy <SRC_URL> <DST_URL>, Subversion sends just command like "please, copy this URL under that URL" and get's response like "done, the new revision number is XXX", so the client doesn't know which files were actually copied. SVNEventAction.COMMIT_COMPLETED is sent by operations that create a new commit (svn copy <URL> <URL>, svn propset property value <URL>, svn commit and others). -- Dmitry Pavlenko, TMate Software, http://subgit.com/ - git-svn bridge > Hello Dmitry > > First of all, thank you for your reply. After I opened the issue, I made a > change to my event handler class and added the > SVNEventAction.COMMIT_COMPLETED and now I see that this event is sent. I > wasn’t expecting that this would sent this event. > My question now is, when performing a url-to-url copy, is this the only > event that will be sent? Shouldn’t more events be sent, particularly, the > event of add? > > I have attached the source code and my working copy format is 1.7. > code.zip <http://subversion.1072662.n5.nabble.com/file/n175990/code.zip> > > > > > -- > View this message in context: > http://subversion.1072662.n5.nabble.com/doCopy-doesn-t-generate-events-tp1 > 75970p175990.html Sent from the SVNKit - Users mailing list archive at > Nabble.com.
