Continuum has nothing to do with all this. It's all the SCM plugin. I'll need to add support for a clientspec name override.
We have a similar 'builder' p4user with anthill. We 'p4 login' that p4user for our 'anthill' unix user and have him set up so that his login never expires. All anthill p4 operations will default to this p4user. You might consider doing the same. The only other way to specify the user is to use the SCM URL which is not a good idea in a multi-developer environment. -----Original Message----- From: Neil Padgen [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 13, 2005 10:16 AM To: continuum-users@maven.apache.org Subject: RE: Cannot add Perforce project to Continuum 1.0.2 Yep, got all that. However, we have a naming policy for our Perforce clientspecs here (project-branch-machine), so I'm trying to persuade Continuum to use that. I'm not sure how to persuade Continuum to use a specified username for Perforce though. Our Perforce license grants us one automated (non-human) user, who is called "background", so all automated processes which use Perforce need to use that Perforce user. It's unlikely that Continuum will run as a user "background", so this will need to be specified.
