[jboss-jira] [JBoss JIRA] (DROOLS-356) KieScanner doesn't work on a KieContainer using a maven version range

[Mark Proctor (JIRA)]

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

Mark Proctor commented on 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.
                
> KieScanner doesn't work on a KieContainer using a maven version range
> ---------------------------------------------------------------------
>
>                 Key: DROOLS-356
>                 URL: https://issues.jboss.org/browse/DROOLS-356
>             Project: Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Mario Fusco
>            Assignee: Mario Fusco
>             Fix For: 6.0.1.Final
>
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira