I'm attach some files with errors, that generated during build:
error-exceptions.txt - is a stack traces for error message only
all-exceptions.txt - is a stack traces for all exceptions, generated in
org.guvnor.common.services.builder.Builder.build()
all-messages.txt - bonus . This is a all
Forgot to mention: messages, shown to user, hides the errors source. In my
opinion, messages should include at least an Exception.getMessage().
--
View this message in context:
http://drools.46999.n3.nabble.com/Too-agressive-scanning-of-classes-in-KieModuleMetaDataImpl-tp4028687p4028720.html
2014-03-14 13:23 GMT+04:00 manstis [via Drools]
ml-node+s46999n4028723...@n3.nabble.com:
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
I agree, reporting could be improved.
The problem is how to programmatically determine why a
NoClassDefinitionFound exception was thrown.
On 14 March 2014 12:35, vektory79 vektor...@gmail.com wrote:
2014-03-14 13:23 GMT+04:00 manstis [via Drools] [hidden
In Drools 6, when org.kie.scanner.KieModuleMetaDataImpl is
initialized, it scans all classes in all dependencies. At my point of view,
it's a too aggressive.
In many situations, scanner catches not only needed modules, but many
modules with testing and provided scopes.
In other side, in
Hi,
I am not sure I completely agree with what you wrote.
In general all the classes defined in all transitive dependencies could
potentially be used in your domain and then should be indexed by the
KieModuleMetaDataImpl. I'd say that something like: provided scoped modules
could be included,
