Currently if someone includes a Publican condition (one in the publican.cfg file) and in the Content Spec (ie [condtion=test]), then the later will be completely ignored which could result in unexpected build errors. As such if both are specified then an error or warning should be produced saying that only one way will work.
Fixed in 1.3-SNAPSHOT build 201311061019 The validator will now print warnings when a condition is used on a node and in the publican.cfg metadata.
This version is now live on the dev/test server.
Confirmed that an warning is produced when there are conflicting conditions. I'd suggest that the error be changed from: A condition has been defined in publican.cfg and as such the condition will be ignored. To A condition has been defined in publican.cfg, and as such the condition defined against the topic or container will be ignored.
Fixed in 1.3-SNAPSHOT build 201311251126 I've updated the warning message to what Matt mentioned above. Note: This version is currently live on the development/test server.
Confirmed new warning message.