Mailing-List: contact continuum-users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: continuum-users@maven.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Cannot add Perforce project to Continuum 1.0.2
Date: Tue, 13 Dec 2005 10:34:20 -0600
Message-ID: <ECFB827E149E9C499CCF16A42C1B64319BA9F4@webifymail01.webify.local>
Thread-Topic: Cannot add Perforce project to Continuum 1.0.2
Thread-Index: AcX/RXlD9y+XyBcJQCywbkSEjLa9/wAjUbwQAAp/y6AAAMIj4AAAaF/Q
From: "Mike Perham" <Mike.Perham@webifysolutions.com>
To: <continuum-users@maven.apache.org>

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. =20

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:Neil.Padgen@mon.bbc.co.uk]=20
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

=20
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.