Hi,
Hudson seems to label a build as "failed", if the "archive artifacts" option is
set, but no artifacts are found. In my particular application this behavior
breaks a build even if it has been built successfully.

Let me explain my scenario in a few words. I have a job that runs nightly
performing a clean build of a project (via Ant). The Ant script recognizes
whether the script has a Release build number (when triggered manually via the
Release plugin) or just an ordinary "snapshot" build number. In the former case,
the script copies the create installer as well as the docs to an _archive
folder, that is subject to the "archive artifacts" in the project's
configuration. Well, in the reoccuring nightly snapshot build, no artifacts
should be archived and hence, nothing is copied to that particular folder.
Consequently, nothing is contained in the _archive folder and thus Hudson
complains that no items could be found when trying to archive artifacts.
Unfortunately, this complain results in a failing of the build.

To prevent from this, I would be glad, if there would be an option that toggles
this behavior: If the option is NOT set, the original behavior is configured
(labeling the build as "failed"). If the option is set, the build status won't
be changed even if the archive step find anything to archive.