Hide Forgot
Description of problem: If you use attribute 'packages' in kie module's declaration of kie base, the packages are filtered using the path they are on rather than package declaration that is in the rule file. Version-Release number of selected component (if applicable): BRMS 6.0.0.ER2 Additional info: I guess this is for performance reasons, since compiling a rule file just to throw it away is a waste. However, I'd expect at least the warning when you compile file with different path and package declaration. At the very least add this warning to documentation, so users know what to expect.
Tomas, For 6, our goal is to enforce package->path consistency the same way that java does. We are probably not covering all use cases yet, but it is expected that if a resource is not properly stored into the correct path, it will result in problems, like the one described in this ticket. So, I would like to suggest closing this ticket as not a bug, but of course, we are open to improve the way we enforce the package->path consistency.
I have opened a bug for documentation as this has to be emphasized in documentation. Closing as NOTABUG.