[ https://issues.jboss.org/browse/DROOLS-1008?page=com.atlassian.jira.plugi... ] Andrew Collins updated DROOLS-1008: ----------------------------------- Description: General: When a kjar has a snapshot version, kie-server will not react to new snapshot versions deployed to a remote artifact repository. The remote artifact repository is only queried the first time after JVM startup, regardless of settings.xml snapshot updatePolicy setting. Retrieving a new snapshot version is only possible through use of KieScanner.scanNow() or recycling the JVM, which will both fetch the new artifact from the remote repository and reload the kmodule in the KieServer JVM. Steps to reproduce: * KieServer and Business Central deployed to separate JVMs, pointing to independent maven repositories. Snapshot updatePolicy should be "always" in KieServer settings.xml. * Deploy new kjar snapshot from Business Central to remote artifactory. (unique version "1") * Start KieServer (verify new snapshot version is pulled from remote) * Deploy new kjar snapnshot. (unique version "2") Expected behavior: * Creating a new container, or invoking updateReleaseId() on existing container will pull latest snapshot from remote artifactory. Actual Behavior * Creating a new container, or invoking updateReleaseId() on existing container, does not query remote artifactory for latest snapshots. Workaround: * Forcing a KieScanner.scanNow() will fetch new snapshot from remote artifactory. * Or, restarting KieScanner JVM will fetch new snapshot from remote artifactory. was: Description of problem: When a kjar is a snapshot version, kie-server will not react to new snapshot versions deployed to a remote artifact repository. The remote artifact repository is only queried the first time after JVM startup. Retrieving a new snapshot version is only possible through use of KieScanner.scanNow(), which will both fetch the new artifact from the remote repository, and reload the kmodule in the KieServer JVM. -- This message was sent by Atlassian JIRA (v6.4.11#64026)