Bug 1035685

Summary: KieScanner doesn't work on a KieContainer using a maven version range
Product: [Retired] JBoss BRMS Platform 6 Reporter: Mario Fusco <mfusco>
Component: BREAssignee: Mario Fusco <mfusco>
Status: CLOSED CURRENTRELEASE QA Contact: Tomas Schlosser <tschloss>
Severity: high Docs Contact:
Priority: high    
Version: 6.0.0CC: etirelli, mproctor
Target Milestone: ER6   
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:20:44 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-11-28 09:57:26 UTC 
It is currently possible to create a KieContainer with a ranged version instead of a fixed one, but this range is not used by the KieScanner that instead consider only the fixed version of the first fetched project.
Comment 1 JBoss JIRA Server 2013-11-28 09:58:08 UTC 
Mario Fusco <mario.fusco> updated the status of jira DROOLS-356 to Resolved
Comment 2 Mario Fusco 2013-11-28 09:58:40 UTC 
Fixed by https://github.com/droolsjbpm/drools/commit/ba79df043
Comment 4 Mark Proctor 2013-11-28 13:15:50 UTC 
Some background for this. When a KieModule is looked up, it allows a version String. The KieModule resolves a jar using Maven. As such engineers expect it to support any standard Maven convention for Strings. But it did not support versions. Further it would lose the original version request; such as -SNAPSHOT. So scanNow would not pick up the latest.

The change allows any Maven version string to be passed, as any engineer would expect, and to ensure that original string is used each time scanNow is called.
Comment 5 JBoss JIRA Server 2013-11-28 13:34:40 UTC 
Mark Proctor <mproctor> made a comment on jira DROOLS-356

Some background for this. When a KieModule is looked up, it allows a version String. The KieModule resolves a jar using Maven. As such engineers expect it to support any standard Maven convention for Strings. But it did not support versions. Further it would lose the original version request; such as -SNAPSHOT. So scanNow would not pick up the latest.

The change allows any Maven version string to be passed, as any engineer would expect, and to ensure that original string is used each time scanNow is called.

The current work around is to create an empty wrapper project, to control deployment updates. This project's pom would be resolved by maven, and thus all version syntax is supported and corrected resolved.
Comment 6 Tomas Schlosser 2014-01-07 08:50:37 UTC 
Verified in BRMS 6.0.1-redhat-2