[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-vcm-dev] .vcm_meta file
|
Your analysis of the problem is absolutely correct.
One of the (uncommitted) work items for the Core team is that they will now
generate something equivalent to the .vcm_meta in the project root. This
not only provides universal support for all providers, but has the added
bonus that zipping up a project will give you something self-descriptive.
This does create a compatibility issue though.
When would you need such support?
Kevin McGuire
"Bryan Stephenson"
<Bryan.Stephenson@meran To: <platform-vcm-dev@xxxxxxxxxxx>
t.com> cc:
Sent by: Subject: [platform-vcm-dev] .vcm_meta file
platform-vcm-dev-admin@
eclipse.org
03/04/2002 10:25 AM
Please respond to
platform-vcm-dev
In the 1.0 VCM the .vcm_meta file maintained information about the project
nature and builders etc. Under VCM 1.0 it was automatically generated on
the first synchronize so would be put under source control. The necessity
for this file in the repository was to support the creation of workspace
projects from repository projects while maintaining the project natures.
There only appears to be support for the .vcm_meta file in the Team 2.0 CVS
implementation. While the examples do not have a get from
source control operation, there is nothing top stop this being implemented.
If so, how is the maintenance of project natures handled or does this
"generic" operaqtion have to be coded per provider.
Bryan Stephenson mailto:Bryan.Stephenson@xxxxxxxxxx
_______________________________________________
platform-vcm-dev mailing list
platform-vcm-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-vcm-dev
