Re: [platform-team-dev] Externally created team private resources

["Vladimir Grishchenko" <vladgri@xxxxxxxxxxx>]

Thanks for the poiner but the reality is we must support 3.0 as this is what most of our
enterprise customers use in the form of RAD6. So unfortunaltely this is not going to work
for us.

Regards,
Vladimir.


----- Original Message ----- 
From: "Jean-Michel Lemieux" <Jean-Michel_Lemieux@xxxxxxxxxx>
To: "Generic team support framework" <platform-team-dev@xxxxxxxxxxx>
Cc: "'Generic team support framework'" <platform-team-dev@xxxxxxxxxxx>;
<platform-team-dev-bounces@xxxxxxxxxxx>
Sent: Tuesday, March 14, 2006 6:13 AM
Subject: Re: [platform-team-dev] Externally created team private resources


> The real solution to team-private files is to use the new EFS support in
> 3.2. This
> allows a team provider *full* control over the files/folders in a project.
> When you
> map/unmap a repository provider you can install your own EFS for the
> project
> and take full control - no more marking as with team private files.
> Cheers,
> Jean-Michel
>
> platform-team-dev-bounces@xxxxxxxxxxx wrote on 03/13/2006 11:51:05 PM:
>
> > Hi,
> >
> > We are facing a problem similar to one described in this bug report:
> >
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=12386
> >
> >
> > This bug is marked as a duplicate of 21128 which has been fixed in 3.1
> M6,
> > would someone kindly describe what was the resolution?
> >
> > In our case team private members are created outside of control of our
> > Eclipse plugins, so they are always created externally in a sense even
> > though it is done in the same VM. Depending on the delta notification
> order
> > Navigator sometimes sees the team private folders before we can mark
> them as
> > team private, as this doesn't fire a delta they stay visible until the
> > Navigator view is restarted.
> >
> > I noticed one workaround for the similar CVS issue was to register a
> > lightweight plugin at startup whose sole task was to mark CVS folders as
> > team-private. Looking at Iworkspace.addResourceChangeListener() -
> > notification order is not specified, although I think it is done in the
> > order of registration. Is this my only option on the Eclipse side? We
> must
> > support 3.0.
> >
> > Thanks and regards,
> > Vladimir.
> > _______________________________________________
> > platform-team-dev mailing list
> > platform-team-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/platform-team-dev
>
> _______________________________________________
> platform-team-dev mailing list
> platform-team-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/platform-team-dev
>