All jars must have a pom.properties in there, for versioning and lookup. Maven built jars
will place that in there for you. We will generate a generic pom.properties for you, if
you are generating a kjar in memory with the programmatic api - but this has very limited
use cases, related to in memory throw away stuff. If it’s a provided jar, then we can only
use what is given. If we were to generate for this, it would mask other problems, and
cause other problems. Such as KieContainer lookup, via ReleaseId.
Mark
On 30 Dec 2013, at 08:15, mayank_io <mayank.kumar(a)gmail.com> wrote:
Hi Vinod,
Adding the ksession tag didn't help. I assumed, doing
newStatelessKieSession() in the code would do the same thing.
When I was trying to extract the console log as requested by you I noticed
this in the log file:
13:35:31.046[main] WARN ClasspathKieProject : Unable to load
pom.properties tried recursing down from/.../target/test-classes/
Taking this further, I added a pom.properties under META-INF/maven under the
resources folder of this project with the following content:
version=${project.version}
groupId=${project.groupId}
artifactId=${project.artifactId}
Once this pom.properties is placed, it runs like a charm!
I wonder though why this file is required and why it cannot be placed
generated automatically if not found?
Thanks,
Mayank
--
View this message in context:
http://drools.46999.n3.nabble.com/rules-users-Unable-to-have-KBase-recogn...
Sent from the Drools: User forum mailing list archive at
Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users