[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-vcm-dev] VCM 2.0 - question ...
|
Boris Pruessmann wrote:
> Hello all,
>
> I am currently trying to develop a perforce integration
> for eclipse.
Great, that would be a useful addition to the team capabilities.
> Taking a look at the current version, I realized that I
> might have a problem because of the way perforce works.
Just to be pedantic, I'd call R1.0 the "current" version, the V2.0 API is
still work in progress and not part of the build; so I'd be inclined to
call V2.0 the near "future" version.
> Here we go:
>
> - Perforce has one rootpath/client for all its operations.
> So, if my root path is c:\perforce all the controlled files
> will be under that path and its subdirectories.
>
> - If I want to have my sources under source control, I have
> to assure that my projects are created under that root path.
> I don't think this is currently possible - at least there was
> no way to specify the team provider during the creation of
> a project, which would be necessary.
If you are dealing exclusively with version-controlled resources then you
can set the workspace to the root path, otherwise (more likely) you can
create projects in a "non-default" location to specify them in the root
path.
I'll leave it up to James or someone to give the definitive answer on
setting up the natures at creation time, but in principle that should be
possible (i.e., create a new project with both the Java and Team nature).
Otherwise, I agree it will have to be made possible.
> - The mechanism of configuring an existing project afterwards
> will not work because of the rootpath problem. The same for
> deconfiguring. If the project is under the rootpath, it's
> under control.
It may be that some projects have a natural nature that cannot be
added/removed for situation such as these.
> I could of course always copy the files between the two
> locations, but I still want to be able to use the tools
> currently available ...
Agreed.
> Any suggestion would be greatly appreciated :)
Regards,
Tim
