Extreme subversion pain

Hi everyone,

Recently we've had some really bad subversion problems. This is with 6.0.4 on OS X, we upgraded our repositories to 1.4 when it asked. We're pretty under the hammer, so I haven't had time to file a lot of JIRA requests, but here's a shortlist:

1. If it encounters a conflict on an update, it will often abort the update, leaving some files on the server.

2. It will occasionally report a conflict where there are no conflicting chunks.

3. Even if I resolve a conflict in the merge conflict window, IntelliJ will leave the merge markers in the file and leave the .mine and .version files (i.e. won't actually resolve the conflict).

4. After an incident like this, I frequently have to restart IntelliJ, since it will occasionally report a series of bizarre syntax errors that I can't get it to fix. For example, variables that are declared on one line are reported as not being found on the next line.

Has anyone seen anything like this? I'm working with a smallish team of people who are relatively new to IntelliJ, I'm working in a startup and I basically convinced everyone that we should use it as our company standard IDE. These problems, in addition to the Ant problems I reported in another thread, look really really bad, and people are now starting to ask: why are we using this instead of Eclipse? This is the final released version, and these are pretty serious bugs. I can put up with the occasional hiccup, but there has been a serious lack of pleasure in my development recently.

18 comments
Comment actions Permalink

Colin Fleming wrote:


3. Even if I resolve a conflict in the merge conflict window, IntelliJ will leave the merge markers in the file and leave the .mine and .version files (i.e. won't actually resolve the conflict).

I have occasionally seen this, but no recipe to reproduce it I'm afraid,
so I haven't filed a bug.


4. After an incident like this, I frequently have to restart IntelliJ, since it will occasionally report a series of bizarre syntax errors that I can't get it to fix. For example, variables that are declared on one line are reported as not being found on the next line.

I've seen this reported elsewhere and have also experienced. I'm pretty
sure there's a workaround that doesn't involve restarting...

Sorry not to be more helpful,
R

0
Comment actions Permalink

I'm now trying to review my changes before doing a commit. I've deleted a couple of directories, when step through the changelist using the left and right arrow icons and it arrives at the directories, it tells me that "service" (the name of the directory) is not of a known filetype, and would I like to assign it a filetype? I can click accept and assign it a type (say, text file) at which point I can't do anything except close the diff window.

Seriously, am I going crazy? Is no-one else having problems with the SVN integration? It's almost unusable for me at the moment. I've never had this degree of trouble with it before. Is it a 1.4 repo issue?

0
Comment actions Permalink

Hello Colin,

I'm now trying to review my changes before doing a commit. I've
deleted a couple of directories, when step through the changelist
using the left and right arrow icons and it arrives at the
directories, it tells me that "service" (the name of the directory) is
not of a known filetype, and would I like to assign it a filetype? I
can click accept and assign it a type (say, text file) at which point
I can't do anything except close the diff window.


This particular problem is not Subversion-specific, and it has been fixed
in Selena (http://www.jetbrains.net/confluence/display/IDEADEV/Selena+EAP)

--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Will this be fixed in a later v6 release as well?

I just noticed that it's also not letting me step through all the changes I have - the compare next file icon is lit up and I know I have more changes, it simply won't let me advance. Is this related?

Lately the command line has given me much more development pleasure than the SVN integration (whether it's specific to SVN or not). I've never had so much trouble with IntelliJ as with v6. I'm the biggest poster boy for IntelliJ around, but all the problems above are driving me crazy and my Eclipse friends are starting to laugh at me.

0
Comment actions Permalink

Hi Dimitry,

The issues Colin reported sound very serious to me (aborted updates).

As we are planning to move from CVS to Subversion and IntelliJ is still our development tool, I think your answer is not acceptable.

The problems Colin encounters make me wonder, if we would run into the same troubles. The integration of version control in IntelliJ must be as flawless as possible, this is very critical to us. So, if these issues are common, they ought to be fixed in the current release of IntelliJ a.s.a.p., and not only in Selena.

If the reported issues aren't to be expected under normal circumstances (I cannot judge this, because we have no experience with Subversion so far) then I could probably live with your statement.

So for a potential subversion migrant, I would appreciate some more explanations about the severeness of the problems and the likelihood that they affect us also, when moving to Subversion. Are these only OS X related - we use Windows machines exclusively?

Let me state clearly, that if Subversion integration in IntelliJ 6 happens to be not stable and plagued with burning issues, we would seriously consider to switch to Eclipse if we do not face serious problems there.

The move to Subversion is mandatory for us due to general policies in our central IT department.

Kind regards

0
Comment actions Permalink

For what it may be worth: We had no serious issues with svn at all and have been using it with Idea for more than a year now (everything in pre-1.4 svn-format, maybe that makes a difference).
The only annoying issue was that file copies done in Idea copied the file without history in svn, but iirc that's now fixed.
Note also that Dimitry refers to only a specific problem (that isn't really that critical imho).

Personally I was forced to use Visual SourceSafe recently and found the integration in Idea to be very lacking. However all the important issues were fixed quite quickly in 6.x minor releases. Naturally to build a fix they need very specific descriptions of the environment and scenarios to reproduce the problems.

0
Comment actions Permalink

Stephen,

Thanks for sharing your experience with SVN and IntelliJ. Generally, I have confidence in JetBrains that they fix bugs and flaws timely also in the current release. However, I wanted to make clear, that I view this for the svn integration particularly important. As version control is daily business and has to be reliable, it is more crucial to us than any other of the recently introduced fancy team features.

We plan to migrate to SVN 1.4, so I hope that the issue isn't related to this in particular. The link Dimitry gave in his post wasn't helpfull for me, as it seems not to point to the issue directly (too busy to search for it right now).

Kind regards

Thomas Gülden
Munich, Germany

0
Comment actions Permalink

We've been using IDEA with Subversion for more than a year now and I must admit we haven't had any of the issues that Colin's reporting. We currently have both 1.3 and 1.4 format repositories, so I wouldn't worry too much about the migration.

0
Comment actions Permalink

We've been using Idea with SVN 1.2 and recently upgraded to SVN 1.4
(we're currently on Idea 6). Haven't seen any major problems but some
annoying issues, like the merge that sometimes doesn't remember that
it's been merged. We have devs on Linux and Windows.
R

0
Comment actions Permalink

It's worth repeating that I've used IntelliJ for a couple of years now, and the SVN integration has always been one of the parts that I've liked best about it. I don't know what has changed to suddenly give me this level of grief. I don't think it's a repo problem since the command line always works flawlessly. The only think I can think of is that it might be a 1.4 repo problem, but I have no way of telling other than to revert my repo. I can't see any JIRA issues that might be related to any of these problems, but then I can't really file JIRAs myself since the problems only occur occasionally and aren't repeatable.

0
Comment actions Permalink

Also, it is not reassuring when all the bug fixes are going towards JUST Selena which is a long ways to go. I would rather that the fixes be added in the next point release for the 6.0 series of the IDE as well.

0
Comment actions Permalink

Are both your server and local repository at 1.4? I remember reading some threads late last year about problems with mixed versions (the problems were about javasvn, actually, so you might see them in Eclipse as well).

I'm not using subversion right now in a multiuser environment (have to cope with sourcesafe for the current project at work, unfortunately), but I've used it with no problems until a couple of months ago (both with 1.3 and 1.4 repositories, svn and svn+ssh).

HTH,
Andrei

0
Comment actions Permalink

I can second that - we recently migrated from CVS to SVN and had a bit of pain on 5.x but after upgrading to 6 have been pretty happy. Still a few things that aren't as nice as CVS (see http://www.jetbrains.net/jira/browse/IDEADEV-8079), but there certainly isn't anything that really upsets me.

cheers
dim

0
Comment actions Permalink

Actually, I'm not sure what version our server repo is at. I'll check, that might be the cause of the problem. Thanks!

0
Comment actions Permalink

Absolutely, especially for things as critical as VCS integration.

0
Comment actions Permalink

For what it's worth, upgrading our repository didn't help. One of the problems is here:

http://www.jetbrains.net/jira/browse/IDEADEV-11435

And this is greatly aggravated by:

http://www.jetbrains.net/jira/browse/IDEA-11786

This might have caused some of the more serious ones:

http://www.jetbrains.net/jira/browse/IDEADEV-7257

Although I think we had some of these problems later than 6.0.2. I can't find the JIRA for the problem that Dmitry talked about.

0
Comment actions Permalink

Colin,

Is this issue part of your problems?
http://www.jetbrains.net/jira/browse/IDEADEV-10572

Jon

0
Comment actions Permalink

Maybe - the bad part of that issue is resolved in IDEADEV-7257. However I think we had problems after 6.0.2, although I can't be sure.

Cheers,
Colin

0

Please sign in to leave a comment.