Created build user.
Created build defintion that uses maven. Build definition workspace owned by build user.
Started build listener and scehduled a build. I have delivered some code that compiles to the stream.
Build fails. When I look in the workspace directory on the build machine, it is empty except for .jazz5 and .flag directories.
So it looks as though the workspace has not been loaded and so no pom and hence a failed build.
Is the workspace automatically updated by the build engine? Is there something I am supposed to set.

There is a flag in the build definition that controls whether or not changes are accepted into the build workspace at the beginning of the build. The "Accept latest changes before loading" check box on the Jazz Source Control tab. Make sure that is checked.

You also need to configure the build's repository workspace so that it flows with the stream whose source you want to build. That is controlled in the editor for the repository workspace, not in the build definition. Make sure that you have set that up correctly.

--
David Olsen, IBM Rational, Jazz Process Team

The checkbox is ticked by default so that was OK.
And the flow target is the correct stream (there is only one at the moment).
And if I create and load a new workspace then the expected files are there.

my error log is
2012-05-15 12:36:14 Fetching files to fetch destination "C:\JazzWS" ...
2012-05-15 12:36:16 Invoking build participant "com.ibm.team.build.maven"
com.ibm.team.build.internal.engine.InvalidPropertyValueException: The location "C:\JazzWS\clock" referenced by property "com.ibm.team.build.maven.projectLocation" does not exist.

Which is correct - it has not been loaded.

You should confirm that the repository workspace used by the build has the right contents. (Open the build definition in the Eclipse client. Click on the "Workspace" link near the top of the Jazz Source Control tab to open the editor for the repository workspace. In the pull down menu near the top of that editor, select Show > Repository Files. Using these gestures guarantees that you are looking at the same repository workspace used by the build and not a different workspace with a similar name.)

If the repository workspace has the right contents, then it is likely a problem fetching the workspace to the build machine. I'm not sure the best way to debug that since I haven't run into that problem much myself. You can start by monitoring the location on the build machine where the workspace is supposed to be loaded (from you log messages I think that's C:\JazzWS in your case) as the build happens. See what, if anything, is fetched during the build.

--
David Olsen, IBM Rational, Jazz Process Team