One side effect I've seen from files not being auto-added and this is
noticeably different than CVS is that if I create a new file and then
"Replace with" latest from the repository that unversioned file is
still in my workspace. CVS, in contrast, would literally replace the
entire contents of that folder with what was in the repository. I'm
not sure that would be fixed by having these new files already marked
as versioned but I can test it.
Bradley
On May 12, 2006, at 2:39 PM, Mark Phippard wrote:
> Bradley Wagner <bradley.wagner@hannonhill.com> wrote on 05/12/2006
> 02:31:36 PM:
>
>> Thanks for that. Mark, was that an intentional decision that ya'll
>> made not to "svn add" newly created Java files or that some
>> underlying SVN policy?
>
> It is probably because we followed the CVS plugin's example here.
> I also
> do not think Eclipse has a Team hook for this, although a general
> Eclipse
> resource event listener could likely be used. This part of the
> code has
> been in Subclipse since long before I started using it.
>
> Johan's patch has been committed and backported for 1.0.2 by the
> way. I
> think his patch covers the only drawback in not auto-adding the files.
> Commit and Synchrnonize show the files and will auto-add them already.
>
> Mark
>
>
> ______________________________________________________________________
> _______
> Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by
> IBM Email Security Management Services powered by MessageLabs.
> ______________________________________________________________________
> _______
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: users-help@subclipse.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Fri May 12 21:07:57 2006