Re: [platform-core-dev] RFC 0002 - .metadata under project content area

[Rodrigo_Peretti@xxxxxxx]

That was not our thought when we proposed moving the metadata to the 
content area. All of the persistent properties would have a unique 
behaviour related to VCM: they could be shared or non-shared. We have no 
special mechanism in mind in order to differentiate properties and I 
believe the goal is that the default would be non-shared but the user 
could change it if wanted.

Rodrigo






Dave_Dykstal@xxxxxxx
Sent by: platform-core-dev-admin@xxxxxxxxxxx
12/11/2001 03:26 PM
Please respond to platform-core-dev

 
        To:     platform-core-dev@xxxxxxxxxxx
        cc: 
        Subject:        Re: [platform-core-dev] RFC 0002 - .metadata under project content area

Rodrigo --

My question was really "what sort of API are we looking at for the 
maintenance of metadata" if we move it to .metadata.  Should the 
persistent properties API be extended to place properties in the content 
area and somehow make a distinction between shared and non-shared?

This distinction might be made by having different plugin-specified names 
for metadata areas -- the plugin owner would be responsible for using the 
appropriate ignore stuff for vcm.  On the other hand there could be some 
core maintained attribute on the property itself.

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