It would greatly simplify clearcase configuration within Hudson if the clearcase
plugin would manage the view name itself and provide Hudson a workspace path
within the view itself.

View name management:

I can't think of a good reason that users should specify the name of the view
that Hudson will create. It would be better if Hudson used a convention for
creating the view name based on the build agent the job is running on, the name
of the job and some unique prefix (specified in global clearcase configuration
setup). This would prevent users from running into issues with the same named
view on different build agents. Also, users should never need to know the view
name in order to configure the rest of the job so why bother having them input
it at all?

Workspace root management:

This may require a change to core Hudson but I think it would be very helpful.
The clearcase plugin should by default make the workspace root the view
directory within the standard workspace. Additionally, it should accept a
relative path within that directory to make the "workspace" so that downstream
configuration can be relative to that directory. This would simplify and
standardize a lot of the non-clearcase configuration of jobs (such as always
including the path to the pom.xml file).