There is no "export" thing. "AltRoots" is the closest you get, but it is still workspace spec specified.
So something else is in order...I see a couple of variations on an idea: creating/updating a workspace on the fly with the correct values is pretty easy. 1. Create a config option that names the existing workspace spec to use for the CI build. This then assumes the user has correctly created one. 2. Create a config option that names the workspace spec it creates to use for the CI build. This then creates/updates the spec. The command then uses the named workspace spec for the sync. -----Original Message----- From: Mike Perham [mailto:[EMAIL PROTECTED] Sent: Monday, November 28, 2005 4:34 PM To: scm-dev@maven.apache.org Subject: RE: [jira] Commented: (SCM-79) Add remaining operations to Perforce provider > - can you add checkouted files in a list in checkout consuler like we > do it in svn provider? I added this and attached an 'svn diff' patch to the issue. I also attached a patch to fix several lingering issues with the commands - 'release:prepare' should work fully now. > - can we checkout files in a specified directory (not only in working > directory defined in Perforce configuration)? Continuum doesn't allow > for the moment checkout in an other directory than continuum working > directory. I see why you are asking for this now. release:perform requires this support since it checks out the tagged code into target/checkout. I don't know how to cleanly do this in Perforce. I will have to think about it but it's going to be ugly unless they have some sort of 'export' command that I don't know about. http://jira.codehaus.org/browse/SCM-79 mike
