#36 p4client task shouldn't limit View specification

open
nobody
None
5
2007-05-29
2007-05-29
No

Currently, the p4client task takes a "view" attribute, but this attribute only sets the left-hand side of a p4 view specification. However, there are times when I want to set the full view specification -- for example:

View:
//std/my/project/trunk/... //my_client/my/project/1.2/...

which will check out code in trunk into the "1.2" directory under my root. (This is a real use case: in this case, I am doing an integration build in preparation for a branch from mainline prior to a 1.2 release.)

To work around this deficiency, I've come up with the "hack" of passing the view attribute the full specification, with a "#" appended to the end. Since the p4client task is just doing a naive concatenation, this comments out the part that p4client automatically produces. e.g.

<p4client
clientname="my_client"
view="//std/my/project/trunk/... //my_client/my/project/1.2/... #"
/>

I think it would make more sense for "view=" to take a full view specification, rather than just the left-hand side.

Would even be cool if <p4client> could accept in its CDATA body a full p4 client specification, e.g.:

<p4client clientname="my_client">
Root: X:\ View: //std/my/project/trunk/... //my_client/my/project/1.2/...
... etc ...
</p4client>

Thanks,
Andrew

Discussion


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks