| Re: Version Control Conundrum [message #57485 is a reply to message #57432] |
Wed, 12 December 2007 12:03   |
cgpadwick
Messages: 7
Registered: December 2007
|
Junior Member |
|
|
With Scott Bolin's help, I figured out why I was having so many
problems with the perforce eclipse plugin. I had a project defined
*prior* to installing the perforce plugin. You have to create the
projects from perforce - perforce doesn't know anything about existing
projects that you already have. Thus when you edit a file, eclipse
asks you if you want to make the file writable, and perforce doesn't
know about it (it doesn't get opened for edit).
To fix this, here's what I did:
-I blew away my project (kept contents, just removed it from
eclipse).
-In the eclipse workbench, I clicked Window->Open Perspective->Other-
> Perforce to open the perforce perspective.
-In the P4 Depots window, I removed all the existing servers. Then I
right clicked in the depot pane and clicked "New Server" and typed in
all the appropriate information.
-Now I was able to see the depot files in the depot pane. I navigated
to the depot folder I wanted, right clicked, and clicked "Import as
Project".
-Then when I switched back to the IDL workbench, my project appears in
the project explorer. Note that the location on the hard disk will be
the same as what was specified in the perforce client spec.
-Now I double click a file and it shows up in the editor. If I then
edit the file, eclipse no longer asks me if I want to edit it; rather,
it is opened for edit in perforce. If I switch to the perforce
perspective then the file appears in the "P4 Pending Changelists"
pane.
You can choose to just show different views too, you don't have to
change perspectives. I tend to just use the default perspectives for
each tool.
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
