[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: [Subclipse-users] "Add to svn:ignore" menu item is disabled for all files

From: Dean Schulze <dean_w_schulze_at_yahoo.com>
Date: 2006-03-15 18:22:43 CET

Disabling automatic build was the key. After doing
that and a few iterations of the add to svn, delete
from svn, commit, restore, add to svn:ignore my
WEB-INF/ dir is all straightened out.

That's a nasty trap to fall into, however. Isn't
there any way to tell svn to ignore things on the
initial import? With CVS that's the only way you can
ignore anything because once something is in CVS you
can't ignore it.

This is a pretty dramatic difference when moving from
cvs to svn. Throw in automatic re-builds and you
really get locked up.

--- Jon Skeet <Jon.Skeet@clearswift.com> wrote:

> > It looks like I'm trapped in a loop from which
> subclipse
> > cannot break free.
> >
> > If I delete the classes/ dir and try to commit it
> complains
> > that I don't have a working copy. If I try to
> update I get
> > an error message that says that "Working copy not
> locked.
> > This is probably a bug.
> > Please report." It is complaining about a
> different
> > directory, however.
>
> Try disabling automatic building, doing an update,
> then deleting the
> directory (within Eclipse's resource view), then
> committing that.
> I suspect at the moment, Eclipse is recreating the
> classes directory and
> getting rid of the .svn directories, so that
> Subclipse doesn't know it's
> got anything to delete.
>
> An alternative, do this part from the command line
> instead, with Eclipse
> shut down so it can't interfere, remembering to do
> an svn delete instead
> of just deleting the directory. (Or use svn delete
> and the url, avoiding
> the working copy altogether. You could do that in
> the Subclipse
> repository browser, in fact.)
>
> > It looks like subclipse is just not ready for
> prime time.
>
> Works fine for me... yes, it can be a bit of a pain
> if you get yourself
> into a muddle, but it's not *that* hard to get out
> of (especially with
> the command line as a backup) and most of your time
> shouldn't be spent
> in that state anyway.
>
> Jon
>
>
> Clearswift monitors, controls and protects all its
> messaging traffic in compliance with its corporate
> email policy using Clearswift products.
> Find out more about Clearswift, its solutions and
> services at http://www.clearswift.com
>
> This communication is confidential and may contain
> privileged information intended solely for the named
> addressee(s). It may not be used or disclosed except
> for the purpose for which it has been sent. If you
> are not the intended recipient, you must not copy,
> distribute or take any action in reliance on it.
> Unless expressly stated, opinions in this message
> are those of the individual sender and not of
> Clearswift. If you have received this communication
> in error, please notify Clearswift by emailing
> support@clearswift.com quoting the sender and delete
> the message and any attached documents. Clearswift
> accepts no liability or responsibility for any
> onward transmission or use of emails and attachments
> having left the Clearswift domain.
>
> This footnote confirms that this email message has
> been swept by MIMEsweeper for Content Security
> threats, including computer viruses.
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail:
> users-help@subclipse.tigris.org
>
>

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Wed Mar 15 18:24:11 2006

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.