Re: [platform-vcm-dev] VCM 2.0 - question ...

["Jean-Michel Lemieux/OTT/OTI" <Jean-Michel_Lemieux@xxxxxxx>]

We should keep an eye on the UI and Core mailing lists since they are currently looking into this exact issue. Not only do we need to configure natures in cool ways at project creation time, but also after the fact (e.g. a project was added from a open source repo without a vcm meta file). Team support will pose an interested requirement on project nature support in the UI:

1. How to define that only one nature out of a set of team project natures can be applied to a project? These semantics are support with natures as of today.

--
Jean-Michel Lemieux

"James Moody/OTT/OTI" <James_Moody@xxxxxxx> Sent by: platform-vcm-dev-admin@xxxxxxxxxxx 11/23/01 11:40 AM Please respond to platform-vcm-dev

To:        platform-vcm-dev@xxxxxxxxxxx         cc:                 Subject:        Re: [platform-vcm-dev] VCM 2.0 - question ...

Regarding the setting of project natures at creation time, this is 
problematic. Not from a core perspective, but from the UI perspective. 
Project creation is driven by the 'type' of project you wish to create; if 
you want to create a simple project, use the simple project wizard. If you 
want to create a Java project, use the java project wizard. If you want to 
create a project that is of two or more types (e.g. a Java project which 
is also a CVS project) you're out of luck, as there is no way to create a 
"Java + CVS" wizard. I do not know if any work is going on in this space, 
but it looks to me that the UI team would have to provide such a generic 
solution, as it is impossible for teams to know of all possible 
combinations of available project natures which might be used together, 
and which might conflict (e.g. CVS and Perforce is invalid on the same 
project).

james





"Tim Ellison" <Tim_Ellison@xxxxxxxxxx>
Sent by: platform-vcm-dev-admin@xxxxxxxxxxx
11/23/2001 10:37 AM
Please respond to platform-vcm-dev

 
        To:     platform-vcm-dev@xxxxxxxxxxx
        cc: 
        Subject:        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

_______________________________________________
platform-vcm-dev mailing list
platform-vcm-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-vcm-dev



_______________________________________________
platform-vcm-dev mailing list
platform-vcm-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-vcm-dev