Should TeamServer read my perforce client mappings?

Hello Steve,
It seems it's a teamserver bug, it has to checkout project using client
mapping.
I created corresponding bug request.
http://www.jetbrains.net/jira/browse/TW-502
Thanks!

"Steve Allan" <takezowest@yahoo.com> wrote in message
news:h511wtgbwin.fsf@stevea-gx270.attachmate.com...

I'm making good progress in getting various projects to build under
teamserver eap 1382. One of my projects requires a slightly more
complex perforce client mapping than the others I've used for testing
so far. When I configured the perforce vcs, I gave it the a depot path
to the root of the project, and the name of a client spec that has the
desired client mappings, but when the files were checked out, the
client mappings weren't used.

>

I imagine I could get the desired results by configuring multiple vcs
components and using the 'Checkout path', but then I'm duplicating the
information that's already in my client spec, which is a required
element in the perforce vcs configuration. And in some cases we have
clients where a few files are ommitted or renamed; that would be
difficult to duplicate in the vcs configuration interface.

>

So I'm wondering what the purpose of the clientspec field is? How is
it being used by TeamServer? It would seem to me that if TeamServer
uses the client spec, there'd be no need for the 'Checkout path' and
'Depot' fields.

>

Thanks for all your help.

>

--
-- Steve