Can you create a unit test that reproduces your issue. Something that follows this: https://github.com/droolsjbpm/drools/blob/master/kie-ci/src/test/java/org/kie/scanner/KieRepositoryScannerTest.java
http://docs.jboss.org/drools/release/5.6.0.Final/droolsjbpm-introduction-docs/html/gettingstarted.html Mark On 30 Jan 2014, at 19:49, Matteo Mortari <matteo.mort...@gmail.com> wrote: > Hello, > in the hope this could save time if someone has been experiencing same issue. > Drools 6.0.1.Final > > I had message "Cannot find KieModule" with kieServices.newKieContainer() with > LATEST or RELEASE , instead of explicit version number (eg: 0.0.1) on a > application where the KIE module Rule artifact project kjar has been > locally-installed from remote Maven repository, that is the right hand side > of this diagram: > http://docs.jboss.org/drools/release/6.0.1.Final/drools-docs/html_single/#d0e933 > > Meaning that before launching Application, I performed > mvn org.apache.maven.plugins:maven-dependency-plugin:2.8:get > -Dartifact=com.acme:X:LATEST > -DrepoUrl=http://nexus-hostname/nexus/content/repositories/releases/ > > Then: > kieServices.newKieContainer() with LATEST, > kieServices.newKieContainer() with RELEASE, > > failed with stack trace: > Exception in thread "main" java.lang.RuntimeException: Cannot find KieModule: > com.acme:X:RELEASE > at > org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:86) > at (...) > > But kieServices.newKieContainer() with a fixed version, eg.: 0.0.2 did indeed > worked OK, if installed in the local .m2 repository. > > To avoid this issue, I found only 3 possible workarounds > 1 use mvn maven-dependency-plugin:go-offline but did not work all of the time > 2 manually ensure maven-metadata-local.xml file is generate in local .m2 > repository > 3 just download manually .jar and .pom of the remote maven repo, and then > install with mvn install:install-file > > In this case, of workaround kieServices.newKieContainer() works OK with all > the version LATEST, RELEASE, and fixed version number. > > Raise jira DROOLS-419 with more details and example projects, please don't > hate me if was just me missing something or not-Drools issue actually > =P > In my defense I had good intentions saving somebody's else time in case same > strange behavior, which is really strange because to me it worked only with > explicit fixed version number, and that was really bizarre ;) > > Hope this helps, > Ciao > MM > _______________________________________________ > rules-users mailing list > rules-users@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________ rules-users mailing list rules-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users
