You can work around this now by having a wrapper project. All to does is have a single
maven dependency on the target project, and in that you specify your maven version
ranges.
Mark
On 3 Dec 2013, at 14:30, Mario Fusco <mario.fusco(a)gmail.com> wrote:
Hi,
the problem with the last code you pasted is that you're passing to the
KieContainer a ReleaseId with a fixed non-snapshot version. Version 1.0.0
can be installed only once in a maven repository so the KieScanner assumes
there's no need to do a further scan. To overcome this problem you should
use a SNAPSHOT version like in:
KieContainer kContainer =
ks.newKieContainer(ks.newReleaseId(
"com.masterit.labs", "my-rules",
"1.0.0-SNAPSHOT"));
I also made it possible to pass range versions to the KieContainer like in:
KieContainer kContainer =
ks.newKieContainer(ks.newReleaseId(
"com.masterit.labs", "my-rules",
"[1.0.0,)"));
but unfortunately I didn't developed this improvement fast enough to have it
included in the final release. It will be part of the next minor release,
but of course in order to use this you will have to increase the version
number of your project before to deploy the new kjar.
I hope this helps,
Mario
--
View this message in context:
http://drools.46999.n3.nabble.com/KIE-Internal-M2-Repository-Access-Denie...
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