starting work on this

Code changed in hudson
User: : kaxelson
Path:
trunk/hudson/main/core/src/main/java/hudson/model/AbstractBuild.java
trunk/hudson/main/core/src/main/java/hudson/model/AbstractProject.java
trunk/hudson/main/core/src/main/resources/hudson/model/AbstractItem/configure-common.jelly
trunk/hudson/main/core/src/main/resources/lib/hudson/project/config-cleanWorkspace.jelly
trunk/hudson/main/war/resources/help/project-config/cleanWorkspace.html
http://fisheye4.cenqua.com/changelog/hudson/?cs=19373
Log:
[FIXED HUDSON-3966] added option to clean workspace before each build as part of advanced project configuration

Code changed in hudson
User: : kaxelson
Path:
trunk/www/changelog.html
http://fisheye4.cenqua.com/changelog/hudson/?cs=19374
Log:
HUDSON-3966: adding changelog message

Rolled back from 1.315 release in rev.19544. See
http://www.nabble.com/attention-all-subversion-users-td24335693.html for the
discussion.

Note that the Mercurial plugin already has an option to delete all nonversioned
files from the workspace before starting. (The .hg/ subdirectory is excluded as
is usual.) I think there is a similar issue open for Subversion. This is more
efficient than deleting everything in the workspace, but may not be applicable
for all situations.

The option to remove all workspace is important to make maven release plugin to
work correctly for the projects, that generate sources e.g. with JAXB. In my
case I commit JAXB sources from Windows environment, which after being
re-generated have different EOF and SVN senses this as uncommitted change, which
in its turn blocks the release.
If the fix is ready, what is the target milestone for this fix?

What is the status of this? I read through the referenced email thread (now at http://markmail.org/message/mcgftdni6cvpca7v) which seemed to end with agreement on the feature but issues with backwards compatibility.

Does this functionality anytime implemented, as I see this issue is being reopened.

Can't this option just call the same function as the "Wipe Out Workspace" feature? If the SCM plugin supports it, then everything will be fine. If it doesn't then it simply won't delete the workspace.

I like Kohsuke's proposal of providing an 'extension point in core to abstract away various "clean" logic'.
http://n4.nabble.com/attention-all-subversion-users-tp393646p393656.html