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

[Rodrigo_Peretti@xxxxxxx]

Dave, I believe you should look at the ignore extension point provided by 
org.eclipse.vcm.core. An example of use is in 
org.eclipse.jdt.ui.vcm/plugin.xml  (not sure why ui and not core) :

<extension point="org.eclipse.vcm.core.ignore">
  <ignore pattern="*.class" selected="true" /> 
</extension>

I believe someone from VCM may have a better answer. Also, I don't know 
how it works on the new VCM story.

Rodrigo






Dave_Dykstal@xxxxxxx
Sent by: platform-core-dev-admin@xxxxxxxxxxx
12/10/2001 11:46 AM
Please respond to platform-core-dev

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

I've been down this path with our plugins and came to the same conclusions 

as Jean-Michel.  We are currently storing non-shared persistent metadata 
using the persistent resource properties.  We are storing shared 
perstistent properties in a plugin-dependent format in a 
.project-properties file in the project content. 

One problem that our scheme doesn't fix is that we would like to have the 
non-shared metadata be packaged with the project on export.  This would 
include things like (for example) remote build system user ids and other 
user-specific settings.  It sounds like this is addressed by having both 
shared and non-shared metadata located in the project content area with 
the non-shared metadata being marked by the plugin as "do not store in 
repository".

What sort of API would we be looking at for this?

-- Dave


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