<Andreas.Krueger@eplus.de> wrote on 02/15/2006 10:53:52 AM:
> This is intended to be a bug report on Subclipse 1.0 RC 4.
>
> I find it more difficult than I would like it to be, to version
Eclipse's
> .classpath and .project files with subclipse.
>
> E.g., with subclipse fresh out of the box and a SVN repository fresh out
of
> the box as well, a "share project" operation on a newly created Java
project
> will not put .classpath and .project under SVN control.
>
> An "add to version control" on the files in the navigator will add them
to
> version control all right, as judged by the svn command line client.
> However, a subsequent "commit" on the entire project still does not
transmit
> the files to the server.
>
> Regards, and thank you for providing fine software
I have never seen it behave that way. When I share a project these files
are always offered to be committed by default. I think others on this
list would concur.
You might check your preferences under Team -> Ignored Resources and see
if they have been added to the global ignore list in Eclipse.
I have attached a screenshot I just made after creating a new project and
doing Team -> Share. The screenshot is of the commit dialog.
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
Received on Wed Feb 15 19:47:57 2006