[jboss-jira] [JBoss JIRA] (DROOLS-1008) KieServer to update container for SNAPSHOT kjar

[Justin Goldsmith (JIRA)]

    [ https://issues.jboss.org/browse/DROOLS-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279982#comment-13279982 ] 

Justin Goldsmith edited comment on DROOLS-1008 at 8/17/16 12:37 AM:
--------------------------------------------------------------------

[~mfusco]
[~andrew.collins]

Any status on this.  I am able to duplicate this error and have to clear out my local .m2 before the snapshot gets updated in business-central on a deployment.
I have the update policy set to always in my settings.xml so I am pretty sure everything is configured correctly

My scenario is slightly different but basically the same
build and deploy kjar to remote nexus - using a seperate settings.xml for this build and a seprate local reposiotry as to not conflict with what BC is using
deploy GAV to BC

The deployment is still the old snapshot


was (Author: jgoldsmith613):
[~mfusco]
[~andrew.collins]

Any status on this.  I am able to duplicate this error and have to clear out my local .m2 before the snapshot gets updated in business-central on a deployment.
I have the update policy set to always in my settings.xml so I am pretty sure everything is configured correctly

> KieServer to update container for SNAPSHOT kjar
> -----------------------------------------------
>
>                 Key: DROOLS-1008
>                 URL: https://issues.jboss.org/browse/DROOLS-1008
>             Project: Drools
>          Issue Type: Feature Request
>          Components: kie server
>    Affects Versions: 6.2.0.Final, 6.3.0.Final
>            Reporter: Andrew Collins
>            Assignee: Mario Fusco
>         Attachments: snapshot_kjar_reproducer.patch
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)