[jboss-jira] [JBoss JIRA] (DROOLS-3090) KieScanner does not work as expected

Ales Dolecek (Jira) issues at jboss.org
Tue Oct 9 07:59:00 EDT 2018


Ales Dolecek created DROOLS-3090:
------------------------------------

             Summary: KieScanner does not work as expected
                 Key: DROOLS-3090
                 URL: https://issues.jboss.org/browse/DROOLS-3090
             Project: Drools
          Issue Type: Bug
          Components: core engine
    Affects Versions: 7.8.0.Final
            Reporter: Ales Dolecek
            Assignee: Mario Fusco


We have published nee version of rules:

{noformat}
2018-10-09 10:44:58,785 INFO  [Timer-2][] ScannerListener Knowledge base scanner SCANNING
2018-10-09 10:44:59,019 INFO  [Timer-2][] ScannerListener Knowledge base scanner UPDATING
2018-10-09 10:45:00,236 INFO  [Timer-2][] KieRepositoryImpl KieModule was added: ZipKieModule[releaseId=cz.dimensiondata.o2:offline-rules:0.0.20,file=F:\GCTI8\assign_manager_2\repository\cz\dimensiondata\o2\offline-rules\0.0.20\offline-rules-0.0.20.jar]
2018-10-09 10:45:00,345 INFO  [Timer-2][] KieScanner The following artifacts have been updated: {cz.dimensiondata.o2:offline-rules:0.0.19=cz.dimensiondata.o2:offline-rules:jar:0.0.20}
2018-10-09 10:45:00,345 INFO  [Timer-2][] ScannerListener Knowledge base scanner RUNNING
2018-10-09 10:45:00,345 INFO  [Timer-2][] ScannerListener Knowledge base scanner RUNNING
{noformat}

As you can see the jar got downloaded to local M2 repository and replace. Yet drools still uses old rules.

We have 3 artefacts:
offline-facts - with classes inserted into operation memory
offline-rules - with rules in 1 DRL file and 2 XLSX file
offline-server - with the application code

offline-server depend on offline-facs (so it can create new insances)
offline-rules depend on offline-facts as well, but with provided scope (so the one on classpath is used)

I have found that Maven has its own caching mechanism so even if new version is published it wont check remote repository more ften than once a day. This can be solved by setting update policy to always.

{code}
<repositories>
	<repository>
		<id>public</id>
		<name>Public Repositories</name>
		<url>https://example.org/nexus/content/groups/public/</url>
			<releases>
				<updatePolicy>always</updatePolicy>
			</releases>
			<snapshots>
				<updatePolicy>always</updatePolicy>
			</snapshots>
	</repository>
</repositories>
{code}

Everything seems configred correctly. Fragments of spring configuration are added.

I'm bit confused what the message:

{code}
The following artifacts have been updated: {cz.dimensiondata.o2:offline-rules:0.0.19=cz.dimensiondata.o2:offline-rules:jar:0.0.20}
{code}

actually means.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)


More information about the jboss-jira mailing list