Subversion 1.8 "--non-interactive" and "--force-interactive" flags behavior
Hi Everyone, I've got a question about "--non-interactive" and "--force-interactive" flags behavior in Subversion 1.8. I'm not subscribed to the mailing list, please put my email in Cc in any responses. We've got java application interacting with svn.exe command line utility. For Subversion 1.7 our authentication behavior was the following: - executing command using svn.exe, for instance "svn udpate" - getting "authentication realm" from process output - destroying process - creating correct credential cache for the obtained "authentication realm" (for instance, correct file with encrypted password in the "auth" folder for Windows) - executing command using svn.exe once again - so that authentication goes smoothly as necessary information is in credential cache With Subversion 1.8 client we can not get "authentication realm" to create correct credential cache information: - if not specifying "--force-interactive" flag or specifying "--non-interactive" flag - process output contains authentication failure message, but only with repository url - not the "authentication realm" - if specifying "--force-interactive" flag - process "hangs" not providing any output - so there is no way to get "authentication realm" from it and then destroy the process So the question is - is it possible to somehow return previous behavior of svn.exe client - so that it does not "hang" but just "waiting" for the "user input" providing necessary "authentication realm" in the output? Or what would you recommend in such situation when authentication is necessary when interacting with svn.exe utility from java application? Is directly specifying "--username" and "--password" keys the only available option? Many thanks, Konstantin -- Konstantin Kolosovsky Software Developer JetBrains http://www.jetbrains.com "Develop with pleasure!"
When file has several conflicted properties "svn info --xml" for that file outputs same "conflict" element several times (for each conflicted property)
Subversion 1.8.10 is used.
I changed several properties of the file in one working copy and commit.
Then I changed also these several properties in another working copy and
update.
This resulted in a file with property conflict status (as expected). But
when I execute "svn info --xml" for this file, "conflict" element is
present in the output the same number of times as the number of conflicted
properties. All these "conflict" elements have the same content.
It seems to be a bug, as schema defined for "svn info --xml" output in
"info.rnc" assumes there could be just 0 or 1 "conflict" elements.
*entry =*
* element entry {*
*attlist.entry, url?, relative-url?, repository?, wc-info?,*
*commit?, conflict?, lock?, tree-conflict?*
* }*
What do you think - is this an issue?
--
Best Regards,
Konstantin Kolosovsky
