[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-core-dev] RFC 0002 - .metadata under project content area
|
deleteContent = false implies that you want ot get rid of the projectness
but want to keep the data. For example, in the unlikely case that you dont
want to use Eclipse anymore 8-\
It cannot be accomplished through the filesystem unless we expose the
location. Currently it is in hte .metadata area which is expressly not
API. If we move the .metadata files up to the content area, then it is
much more apparent but we would still have to declare that this is the seat
of projectness. Deleting the .metadata would then the the same as
deleteing the project but not deleting the content.
Users can sort of leave orphan projects around by deleting the content. If
you delete the content and the project is still in the workspace, Eclipse
will notice this and say "wow, all the content for that project is gone.
Guess the user wanted to remove those files" and you would end up with an
empty project. If hte project is not in the workspace, you end up with a
random set of metadata somewhere in the user's disk space.
Jeff
Jeff --
What's the point of having a "deleteContent = false" option? Why would
this be useful? I'd find it much more useful to be able to hide a project
(or sets of projects) rather than to just delete the metadata. Deleting
metadata is a potentially catastrophic operation and for some reason it
sounds too casual here <g>. Maybe it should be accomplished through the
file system only and not through an api?
I like this notion of discovery.
Can't users leave orphan metadata now by deleting a project from the file
system? or does core recognize this and recover?
-- Dave
_______________________________________________
platform-core-dev mailing list
platform-core-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-core-dev
