capabilities of autoprivate

Does the autoprivate.cfg file allow the inclusion of more than a file or directory name? For example, I would like to be able to mark all html files private in one directory, but allow them in all others.

So far, my tests have not been successful. I have attached the autoprivate.cfg file I am using for testing.

Can I pull this off using the autoprivate.cfg file, or will I need to incorporate this functionality into an external task?

I am using TeamSite 5.0.1 SP1 on Solaris.

Thanks,
Robert

Edited by RobertPisor on 04/07/03 11:46 AM (server time).

Find more posts tagged with

Comments

james1

I think that autoprivate.cfg operates only on filename, without regard to what directory (or workarea or branch) a file is in...?

-- James

--
James H Koh
Interwoven Engineering

RobertPisor

Thanks, James. That is exactly the behavior I'm seeing.

Robert

Johnny

Id really like to know if there is a feature request/ or even better enhancement in 6.0 regarding the autoprivate.cfg functionality.

It would be much more flexible if it was able to work with regex patterns on vpaths rather than specific filenames or directory names.

There are certain situations when I would need to mark all files/directories private under a specific location, but under other locations the same type of file should not be private.

My specific purpose is for J2EE virtualisation.

Compiled code in versioned in TeamSite as an .ear file.
However to virtualise we expand the .ear file into an already existing directory structure. It would be great if I could mark certain areas as private.

Essentially autoprivate.cfg would be vastly more flexible if it operated like submit.cfg.
It would make it easier to maintain with one less syntax to learn.

Also the current way is a blanket one for all approach.
If one type of file should be private for a website/branch but not for another... well theres not much you can do about it

John Cuiuli

james1

> Id really like to know if there is a feature request/ or even
> better enhancement in 6.0 regarding the autoprivate.cfg
> functionality.

autoprivate.cfg hasn't changed in 6.0, but there are several open feature requests regarding it:

36031 - should use regexes
34323 - per branch
33980 - support full directory path, not just file/directory basename

Hope this helps.
-- James

--
James H Koh
Interwoven Engineering

Johnny

Great... All three are what I am asking... now I can just sit back and wait Smiley Happy

John Cuiuli

Adam Stoller

Nope - now you need to have your customers contact Support to register their interest in such enhancements - and thus help propell the request up on the stack of thousands of other requests

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Johnny

I know that bit... it was just tongue and cheek Smiley Happy

John Cuiuli

RonaldV

Still waiting, are you?