2014-03-14 13:23 GMT+04:00 manstis [via Drools] <[hidden email]>:
The messages are produced as a consequence of your project's dependencies.For example:Verification of class org.hibernate.metamodel.source.annotations.JandexHelper failed and will not be available for authoring. Please check the necessary external dependencies for this project are configured correctly.This is caused by failure to effectively instantiate JandexHelper (see here).
You are right. But when I see, that org.hibernate.metamodel.source.annotations.JandexHelper can't be validated, how I can distinguish what exactly going wrong?Now I can determine, that ClassLoader doesn’t find class org.jboss.jandex.AnnotationInstance in debug only.
If a class cannot be instantiated then it is not available for rule authoring. We show the warning to alert the user.The Project Editor only exposes course grained features for the average user. You can edit the underlying pom.xml, adding whatever fine-grained exclusions you may require, for your project using the Administration Perspective.Yes. I tried exclusions. It's really work now. Thank you to point me it feature.I just missed the last changes.There are some occasions when you receive an error popup. We are currently working to address this (they'll become errors in the Problems Panel).With kind regards,Mike
View this message in context: Re: [rules-users] Too agressive scanning of classes in KieModuleMetaDataImpl
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users