-
New Feature
-
Resolution: Unresolved
-
Trivial
-
None
-
Platform: All, OS: All
I have 3 requests for enhancement.
+++ View creation /config creation script other than standard mkview:
It would be nice if we could point to another script to run to generate the
view and config spec. (Lot of businesses have created those kind of scripts)
+++ Make $CLEARCASE_VIEW and $CLEARCASE_VIEWPATH available in load rules
Currently I cannot use the options $CLEARCASE_VIEW and $CLEARCASE_VIEWPATH in
the load rules or vob path.
I found no other way to do lshistory then to add a view centric path. Currently
I need to hard code the view name. Would like to use the standard parameter.
This feature and the next one are mutual exclusive. If you implement one, the
need for the other goes away or is lessened. I personally prefer the -avobs
solution.
+++ option to export $CLEARCASE_AVOBS and have lshistory use -avobs instead of -
all
In dynamic views you can specify a $CLEARCASE_AVOBS variable to group a set of
vobs to search in (usefull in a site with 800+ vobs)
Would be nice if $CLEARCASE_AVOBS is set or specified, lshistory would use -
avobs instead of -all
I think you may be best off forking the plugin and implementing the
functionality you want there - I don't think I'll be adding any of this to the
main ClearCase plugin in the near future.
I'm still confused about the second/third request - this, obviously, relates to
issue 4222. Why do you need "/view/my_viewname/vobs/xpuModule" instead of
"/vobs/xpuModule"?