[jboss-jira] [JBoss JIRA] (DROOLS-1008) KieServer to update container for SNAPSHOT kjar
Andrew Collins (JIRA)
issues at jboss.org
Wed Dec 16 12:00:03 EST 2015
[ https://issues.jboss.org/browse/DROOLS-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142031#comment-13142031 ]
Andrew Collins commented on DROOLS-1008:
----------------------------------------
Attached patch to master that includes kie-server integration test to demonstrate this issue. The failing tests should pass when this feature is implemented.
After debugging, the snapshot resolution against the remote repository only happens because a new MavenRepository is created from KieRepositoryScannerImpl.scanNow() that has a new RepositorySystemSession. Am not completely familiar with RepositorySystemSession, but I would think the session should live as long as it does attached to Aether, and should be terminated following KieContainer creation.
> 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: Edson Tirelli
> Attachments: snapshot_kjar_reproducer.patch
>
>
> 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. Updating a KieContainer to a newer snapshot version is only possible through use of the KieScanner, 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)
More information about the jboss-jira
mailing list