Subversion checkout fails (Irida 3296)
Just installed 3296 and tried to checkout my project but unsuccessfull. It says "Authorization failed" (can provide stacktrace from log). svn4Idea plugin with IDEA 4.5 works fine.
Is intergrated Subversion plugin working somehow or not? Any ideas?
Please sign in to leave a comment.
In article <27591559.1114086249152.JavaMail.itn@is.intellij.net>,
Dankoldyr <no_mail@jetbrains.com> wrote:
I STRONGLY recommend you not use the subversion plugin at all right now.
See this bug: http://www.jetbrains.net/jira/browse/IDEA-1105
Though javaSVN does the work right, IDEA is not implementing the process
of moving files around correctly and you CAN end up with a corrupted
repository.
Use at your own risk.
That said, you can't browse a subversion repository unless you're using
a very specific protocol which I have yet to discover:
http://www.jetbrains.net/jira/browse/IDEA-1172
Also even if you tried to do a check out and it worked somehow, if your
repository is remotely big you'll hit this:
http://www.jetbrains.net/jira/browse/IDEA-1228
But... what the heck do I know... If I keep going I'll get slammed again
for even mentioning subversion.
R
I don't care about these bugs. My brackets are on the wrong line:)
"Robert S. Sfeir" <robert@codepuccinoNOSPAM.com> wrote in message
news:robert-20B647.09015521042005@mail.intellij.net...
>
>> Just installed 3296 and tried to checkout my project but unsuccessfull.
>> It
>> says "Authorization failed" (can provide stacktrace from log). svn4Idea
>> plugin with IDEA 4.5 works fine.
>> Is intergrated Subversion plugin working somehow or not? Any ideas?
>
>
>
>
>
>
>
Poor, poor Robert. We might have slammed you too badly on the previous subversion thread. It's not like I don't want to see the subversion bugs fixed.
I use subversion as my day-to-day version control, and it's really a pity that I can't use the IDEA integration right now. Trouble is, thanks to your effort, numerous (critical) bugs have been discovered on the current implementation, and I'll be shying away from the svn plugin until they're fixed.
Problem is, svn integration isn't the only thing broken right now. As I mentioned in the previous thread, code formatting is seriously broken too, as many other important features. The difference is, I have alternatives for my svn needs (Tom, I love you), but I'm short of options when the issue is code generation and formatting.
Bottom line, I trust JetBrains to line up the svn bugs in the right priority, and I trust you to keep pushing them to fix this. In the meanwhile, I'll throw my voice somewhere else :)
No worries, word on the street is that work on fixing the Subversion
plugin has already started.
Thanks for the sympathy :)
R
Thank you for answer. Will wait for fixed, to use it as soon as possible.
In article <29619526.1115146884600.JavaMail.itn@is.intellij.net>,
koldyr <me@koldyr.com> wrote:
I was told this was fixed in 3316 but I haven't tested it yet since I've
been at a conference. Will try it sometime in the next 2 days.
R
Robert S. Sfeir wrote:
I couldn't check out from my svn+ssh repo with 3316 last night :(
In article <d59fkn$vj5$1@is.intellij.net>,
Mark Derricutt <mark@talios.com> wrote:
Hum... I can do that... but how are you doing it?
R
Robert S. Sfeir wrote:
Using the checkout from svn menu item, typed in a user/password ( no key
configured yet ).
Just thinking, the server was rebuilt and has a mismatched keystring in
one of my local .ssh/authorized_keys files ( i fixed .ssh, but .ssh2 is
still wrong ).
So command line ssh complains, but lets me through anyway... it might
be that.
In article <d59ggh$37n$1@is.intellij.net>,
Mark Derricutt <mark@talios.com> wrote:
Yeah it's definitely that, the problem is not idea in this case, it's
javaSVN, you might want to keep your repository as is and let
Alex(at)tmate(dot)org know about it.
R
Robert S. Sfeir wrote:
Well, all I need to do is delete the host entry in the file, so that ssh
will "accept the new host identifier".
In article <d59i4t$b4o$1@is.intellij.net>,
Mark Derricutt <mark@talios.com> wrote:
Right, but javaSVN should handle this or at least throw an error and
complain so that idea can display the problem so you're not guessing as
to why it's not working.
R
Robert S. Sfeir wrote:
True. Will forward the details to the tmater's when I get home from work...
In article <d59ila$c87$2@is.intellij.net>,
Mark Derricutt <mark@talios.com> wrote:
Incidentally that exception you got was most likely due to a move
performed in IDEA, which went wrong, while running the subversion
plugin. Olesya said that's fixed too, need to check it.
R