[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-vcm-dev] Disallow deleting .project?
|
Our system will delete the file externally and refetch a read-only copy from
our repository
after the file is added or checked in. This ensures some internal tables
are correctly
initialized/updated. Is there any issue with this behaviour.
Bryan Stephenson
mailto:Bryan.Stephenson@xxxxxxxxxx
----- Original Message -----
From: <Kevin_McGuire@xxxxxxx>
To: <platform-vcm-dev@xxxxxxxxxxx>
Sent: Thursday, March 21, 2002 7:03 PM
Subject: Re: [platform-vcm-dev] Disallow deleting .project?
>
> We *used to* overwrite the java.io.file and do refreshFromLocal.
> For a provider that already has a client (e.g. that they were just
> calling
> from JNI), they might go that route. So question is whether
> refreshFromLocal looks ok under this condition.
>
>
>
>
>
>
> John_Arthorne@xxxxxxx
>
> Sent by: To:
> platform-vcm-dev@xxxxxxxxxxx
> platform-vcm-dev-admin@ cc:
>
> eclipse.org Subject:
> [platform-vcm-dev] Disallow deleting .project?
>
>
>
>
> 03/21/2002 12:48 PM
>
> Please respond to
>
> platform-vcm-dev
>
>
>
>
>
>
>
>
> Just a quick poll... I'm considering making it impossible to delete the
> .project file via Core API. Basically, calling delete on the file would
> throw a CoreException explaining that deleting the file isn't permitted.
> You would of course still be allowed to delete it when the project is
> being
> deleted.
>
> Would this in any way hinder the work that team providers do when
> loading
> changes to this file? I would assume you just call setContents, rather
> than delete followed by create.
>
> _______________________________________________
> 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
