I'm not a developer for subversion but I've got to chime in on this....
While I see what you are trying to do ... I don't think that it is a good
idea. If you want a clean set of files then create yourself a new working
directory. If you run this "svn clean" and you forgot to add some files to
source control then you are going to have some of your code deleted. I
doubt that this is want you want.
I know that if you are using Eclipse then you have to create a new workspace
and all of that for this new working directory that you want for a clean
build. Other tools may have similar problems (e.g. additional work). What
is why I would recommend using Ant and keeping the ant script checked into
the repostory along with the source. The performing a clean build would
amount to something like:
prompt> svn checkout svn://server/project/trunk .
lots of output here from subversion
prompt> ant
-----Original Message-----
From: Casper Hornstrup [mailto:ch@csh-consult.dk]
Sent: Friday, March 04, 2005 2:13 PM
To: users@subversion.tigris.org
Subject: Feature request: svn clean
Hi.
When working on a change that requires a full rebuild to be properly tested
or when making releases would be very helpful to be able to convert an
existing
working copy into what would have resulted from a clean checkout from the
repository. Svn clean would basicly be a superset of svn revert -R. In
addition
to revert, it would delete all unversioned (usually generated) files in the
working copy.
Can I file an issue on this?
Casper
Received on Fri Mar 4 20:50:24 2005