Hi it works, only about 20 lines of code.
One thing to remember to use BasicAuthenticationManager to avoid any filesystem manipulation - because now each time I do SVN update TortoiseSVN ask me login/password. PS. articles seems a little bit out of date - in example used HashMap where now is SVNProperties should be provided. But still very helpfull Dmitry Pavlenko-2 wrote: > > There's a good article: > > http://wiki.svnkit.com/Committing_To_A_Repository > > In short: you create an editor and describe changes. Usually SVN crawls > your working copy to form > correct editor calls sequence; but you can emulate the working copy by > providing correct calls > sequence. > >> Yes, something like this. >> >> PS. I not familiar with SVN under the hood, if there are some good >> documentation about SVN internal principles I will be very thankful if >> you >> give links for it >> >> Dmitry Pavlenko-2 wrote: >> > Hi, >> > Do you mean a possibility to commit without working copy creation? >> > >> >> I'm new to SVNKit and I found a way to commit to remote SVN repository >> >> few >> >> .sql "files" that is actually only in-memory to make backups. >> >> >> >> Is it possilbe to do such actions with SVNKit? And if yes what >> direction >> >> I >> >> should look? > > > -- View this message in context: http://old.nabble.com/Is-commit-from-in-memory-to-remote-SVN-possible--tp34072747p34080937.html Sent from the SVNKit - Users mailing list archive at Nabble.com.
