The integrity documentation says this regarding combining sandbox scope definitions:
Using Logical Operators to Define Sandbox Member Scope
You can also combine Sandbox member scope selections using logical AND or OR operators, and invert Sandbox scope selections by preceding each member selection with a ! character. An AND operator is specified as a --scope option. For example, to transfer project members with the member attributes Alpha AND Beta, specify --scope=attribute:Alpha--scope=attribute:Beta. An OR operator is specified as a comma between values in a --scope option. For example, to transfer project members with member attributes Alpha OR Beta OR GA, specify --scope=attribute:Alpha,attribute:Beta,attribute:GA. You can combine logical operators to create more complex Sandbox scope selctions. For example, to transfer project members with member attributes Alpha OR Beta OR GA AND name .java, specify --scope=attribute:Alpha,attribute:Beta,attribute:GA--scope=name:.java.
I tried this scope definition:
--scope=path:path1/,path:path2/--scope=!name:*.bak
Expecting this to mean: path1 OR path2, excluding *.bak files. Instead, the path2 isn't included in the scope.
How is this actually supposed to work? I am using Integrity 11.2
