We've noticed a bit unexpected behaviour using the valueSet attribute of mm:compare (new in mmbase 1.7).
The following situation:
<mm:import id="a">a</mm:import>
<mm:compare referid="a" valueSet="a,b"> a is found in a,b. </mm:compare>
<mm:compare referid="a" valueSet="a,b" inverse="true"> a is not found in a,b. </mm:compare>
You would expect only "a is found in a,b" would be printed, but they are _both_ printed.
After inspecting the code of CompareTag.java we concluded that inverse="true" is currently being interpreted as 'not a' is in 'a,b' and not as 'a is not in a,b' but this is not as we expected.
I think the behaviour of mm:compare should be different from what it is now if you use both valueSet and inverse. I've filed it as bug #6411
groetjes,
Simon
