Different Projects with Different Schematron Validations

[HSBOracle]

I use different projects each of which uses different Schematron validations. I'm getting unexpected validation errors in oXygen, and it looks like MAYBE that when I switch projects, the schematron from the previous project maybe trying to validate a file in the current project I'm working in. Is this possible? Is there an equivalent for "clearing the cache" between projects using different Schematron validations? Thank you.

[chrispitude]

I use different projects each of which uses different Schematron validations. I'm getting unexpected validation errors in oXygen, and it looks like MAYBE that when I switch projects, the schematron from the previous project maybe trying to validate a file in the current project I'm working in.

I can't be 100% sure, but it seems like MAYBE this happens to us too. When I switch from one project to another, sometimes I see errors pop up about unresolved key references that I think might occur transiently as Oxygen switches from one project to another. I haven't yet tried to reproduce this in a controlled way (perhaps open editing windows or open maps in the DITA Maps Manager?) but next time it happens, I'll take a closer look at what windows/views were open at the time.

[HSBOracle]

We have found the culprit in our case. We use two different projects to work on documentation for two different products with different documentation standards in one instance of Oxygen. One of those requires a plug-in that the other doesn't. However, the plug-in affects editing across projects. Our solution is to disable the plug-in when working in the dita files that don't require it. This is done by navigating to Options > Preferences > Plugins and then disabling the plug-in as needed. It's slightly clunky, but easy enough to do.