4 comments
Comment actions Permalink

There are two plugins because they follow two different paths to the same
problem.

The PerforceDirectPlugin doesn't ues the VCS API provided by IDEA. It
listens to your refactorings and updates the perforce changelist as soon as
you take some action inside IDEA. This is a lean mean plugin and works
pretty well. Probably Richard can give a better description on this one.

The PerforcePlugin uses VCS api, this one keeps the changes in IDEA's
LocalVcs till you actually submit from inside IDEA. So you have to checkin
projects from idea itself. This one provides file status coloring, change
marking, over all project change dispay using the checkin dialog etc. All of
which is possible because of the VCS API and this plugin is closer to the
CVS integration IDEA provides by default.

They both work in EAP builds and you should pick one up depending on your
work habit. If you prefer checking in things from p4win then the "Direct"
plugin is the one for you. If you are comfortable with checking in from IDEA
then you can use the PerforcePlugin.

-Dash.

"Kashif Noorani" <no_mail@jetbrains.com> wrote in message
news:19885087.1090963023691.JavaMail.itn@is.intellij.net...

Why are there two perforce plugins for IDEA? And which one is more

suitable for EAP builds?


0
Comment actions Permalink

Your description is absolutely perfect.
Including the plugin decision reasoning.
Each plugin has also its own list of minor featurettes
that may make the user's life easier (P4DP - support for
P4CONFIG (a 'must' for my work), sync checked-out file, etc.)

r.

Debabrata Dash wrote:

There are two plugins because they follow two different paths to the same
problem.

The PerforceDirectPlugin doesn't ues the VCS API provided by IDEA. It
listens to your refactorings and updates the perforce changelist as soon as
you take some action inside IDEA. This is a lean mean plugin and works
pretty well. Probably Richard can give a better description on this one.

The PerforcePlugin uses VCS api, this one keeps the changes in IDEA's
LocalVcs till you actually submit from inside IDEA. So you have to checkin
projects from idea itself. This one provides file status coloring, change
marking, over all project change dispay using the checkin dialog etc. All of
which is possible because of the VCS API and this plugin is closer to the
CVS integration IDEA provides by default.

They both work in EAP builds and you should pick one up depending on your
work habit. If you prefer checking in things from p4win then the "Direct"
plugin is the one for you. If you are comfortable with checking in from IDEA
then you can use the PerforcePlugin.

-Dash.

"Kashif Noorani" <no_mail@jetbrains.com> wrote in message
news:19885087.1090963023691.JavaMail.itn@is.intellij.net...

>>Why are there two perforce plugins for IDEA? And which one is more


suitable for EAP builds?

0
Comment actions Permalink

Thanks for the excellent description, Debratha. I have been using both plugins and as you said the Direct plugin is lean and mean. The one problem that I have had with it is that it adds changes directly to the "Default" changelist rather than given an option. Otherwise, it would be 100% functional.

I like the sound of the VCS plugin. I would love to use Perforce from within IDEA. However, so far I am getting a bunch of exceptions when I try to use it. Undoubtedly, this is due to my own fault. It would be awesome if the plugin was idiot-proof :)

0
Comment actions Permalink

The VCS plugin also gives you more "integration" in the editor. I used to just use the External Tools to do all my p4 work but I like the markup that appears in the editor window showing me what has changed in a given file.

All the extra, real-time sync'ing can put a drag on the project but I like the extra integration. Auto-adding into the depot and auto-check out is nice too.

0

Please sign in to leave a comment.