Perforce vs Subversion

I figured since JetBrains has had to screw in support for a number of version control systems you may have a strong opinion. We are looking at finally moving away from CVS to either Perforce or Subversion and I was just shopping for opinions. I remember once reading that the preference seemed to be Perforce inside JetBrains, but didn't know if that had changed with more exposure, unless Alexander was the only one really exposed to Subversion.

7 comments

I'm not an expert, but 2 weeks ago I switched from CVS to SVN, and I have no other way of saying that it sucks, but ofcourse, I might have done something wrong...

For SVN support, a lot of features are not implemented, like checking in a project. I used turtoiseSVN for doing that, but for doing that, it uses a putty connection with a public/private key. The syntax is something like svn+ssh://@/]]> . Mind the 'name_of_connection' parameter, since this is the name of the connection in putty, not the hostname. In IntelliJ however, this is the name of the connection, but since the project is created using turtoiseSVN, the projects seem to be incompatible. The changes etc are visible from within IntelliJ, but updating,checking in,etc is not possible. At least, not in my configuration.....

(I don't have any problems when using Eclipse btw, but...well, let's don't go there :) )

0

Hi,

You mean adding new project into repositiry right?
Also no incompatibilities between IDEA and TortoiseSVN was encountered, can you post more details? What build of IDEA you are using?

I think somewhere in IDEA builtin Eclipse users detection mechanism... May be it is specific keystrokes, and then IDEA starts ti simulate Eclipse buggy behaviour but look like not in the same places :(

0

Hello Erik,

EP> I'm not an expert, but 2 weeks ago I switched from CVS to SVN, and I
EP> have no other way of saying that it sucks, but ofcourse, I might
EP> have done something wrong...
EP>
EP> For SVN support, a lot of features are not implemented, like
EP> checking in a project. I used turtoiseSVN for doing that, but for
EP> doing that, it uses a putty connection with a public/private key.
EP> The syntax is something like
EP> svn+ssh://@/ . EP> Mind the 'name_of_connection' parameter, since this is the name of EP> the connection in putty, not the hostname. In IntelliJ however, this EP> is the name of the connection, but since the project is created EP> using turtoiseSVN, the projects seem to be incompatible. The changes EP> etc are visible from within IntelliJ, but updating,checking in,etc EP>]]> is not possible. At least, not in my configuration.....

Have you upgraded to IntelliJ IDEA 5.1? It contains fixes for many problems
in the Subversion plugin.

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


0

I have no experience with Subversion but I can say that I love Perforce and
the IDEA integration is very good. Of course our previous SCM tool was PVCS
so I was easy to please:) Seriously though, I use Perforce over a VPN and it
is easy to use and fast from either P4Win(or P4V) or the IDEA integration.
The Perforce web viewer is very handy too when you just need to look at some
docs.

"Peter Thistleton" <no_mail@jetbrains.com> wrote in message
news:23722337.1139809635115.JavaMail.javamailuser@localhost...
>I figured since JetBrains has had to screw in support for a number of
>version control systems you may have a strong opinion. We are looking at
>finally moving away from CVS to either Perforce or Subversion and I was
>just shopping for opinions. I remember once reading that the preference
>seemed to be Perforce inside JetBrains, but didn't know if that had changed
>with more exposure, unless Alexander was the only one really exposed to
>Subversion.


0

We use perforce here and in general I think the feelings are negative
about it. The IDEA integration is necessarily weak because the only API
into perforce is execution of command-line tools, which fail for stupid
and unpredictable reasons. Perforce doesn't have good support for
refactoring (try moving a file when someone else has it checked out). I
don't know much about SVN but I imagine that it's better.

Peter Thistleton wrote:

I figured since JetBrains has had to screw in support for a number of
version control systems you may have a strong opinion. We are
looking at finally moving away from CVS to either Perforce or
Subversion and I was just shopping for opinions. I remember once
reading that the preference seemed to be Perforce inside JetBrains,
but didn't know if that had changed with more exposure, unless
Alexander was the only one really exposed to Subversion.

0

We used Subversion with IJ 4.5 --> 5.1 until just recently here with no
problems.

Now we switched to Perforce.

The main pro of Subversion is the model - you change anything you want
(on-line or off-line) and then submit. At any time you can do a diff,
even off-line, since SVN maintains a copy of every file.

The main pro of Perforce is speed. At least in our environment updating
with SVN took around 5-10 minutes (even when there were no to very few
changes), whereas with Perforce it's about 3 seconds.

A huge discussion can be conducted on SVN / P4, a discussion we had in
house, but usually it will boil down to specific needs and of course
price. I have several friends who use SVN at home and one of the reasons
(not the only one, not starting a holy war here...) is that it's free.

Amnon

0

Hello Dimitry,

Yes, I'm using IntelliJ 5.1, but the configuration in IntelliJ seems way different than the one I use with Turtoise (eg, with IntelliJ, is store a password in IntelliJ.. in Turtoise, I created a private/public key, so I can login without using a password.)

0

Please sign in to leave a comment.