Description of problem: KieRepositoryImpl.getInternalKieScanner swallows exceptions without printing an error. It is assumed that when the ScannerFactory cannot create a KieScanner, kie-ci is not on the classpath. While this may be the case, there could be other possibilities. In addition, there is not outward sign that anything bad occurred until the application fails to load a maven based kjar. https://github.com/droolsjbpm/drools/blob/master/drools-compiler/src/main/java/org/drools/compiler/kie/builder/impl/KieRepositoryImpl.java#L124 It would be useful if, at the very least, some log is printed saying the scanner couldn't be initialized with a portion of the exception. Version-Release number of selected component (if applicable): 6.0.0+ How reproducible: Consistent Steps to Reproduce: 1. Attempt to utilize kie-ci functionality when kie-ci is not on the classpath 2. Everything works 3. Maven repo access silently fails Actual results: Maven repo access silently fails Expected results: An error in the log noting the exception and that there's a problem, or even a proper exception. Additional info:
I agreed with Adam that adding a warning there will overwhelm with useless messages all users who don't need/want to use kie-ci.