Bug 1007977

Summary: KieRepository doesn't check if there are new snapshot kjar deployed on the maven repo when creating a new KieContainer
Product: [Retired] JBoss BRMS Platform 6 Reporter: Mario Fusco <mfusco>
Component: BREAssignee: Mario Fusco <mfusco>
Status: CLOSED CURRENTRELEASE QA Contact: Tomas David <tdavid>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0.0   
Target Milestone: ER4   
Target Release: 6.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-06 20:16:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mario Fusco 2013-09-13 16:28:47 UTC 
Description of problem:

When new snapshot kjar are deployed on a maven repo and the kiescanner is not enabled, a newly created kiecontainer referring to that snapshot releaseId actually uses the old kjar (cached in the KieRepository) instead of downloading the new one from the maven repo.

How reproducible:

Always

Steps to Reproduce:

A pull request reproducing this issue has been provided here:

https://github.com/droolsjbpm/drools/pull/248/files

Actual results:

The 2nd KieContainer uses the old kjar instead of downloading the new one deployed in the maven repository.

Expected results:

when creating a new KieContainer it should check if a new snapshot has been deployed in the maven repo and then use it.
Comment 2 Mario Fusco 2013-09-20 10:21:18 UTC 
Fixed by https://github.com/droolsjbpm/drools/commit/b09e981f1
Comment 3 Tomas David 2013-10-21 10:01:03 UTC 
Verified on BRMS 6.0.0.ER4.