[jboss-jira] [JBoss JIRA] (DROOLS-906) Kiescanner do not find updates in the KieContainer if the current RELEASE of a maven artifact change selecting an older version

[Mario Fusco (JIRA)]

     [ https://issues.jboss.org/browse/DROOLS-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mario Fusco resolved DROOLS-906.
--------------------------------
    Resolution: Rejected


If I'm getting this correctly, you're trying to control the version of the kjar used in production through the maven repository metadata. This is not what that metadata is build for at all. It can be "refreshed" (= deleted and regerenated) at any time. 

In case I'm misunderstanding your use case, please feel free to reopen this ticket and better clarify it.



> Kiescanner do not find updates in the KieContainer if the current RELEASE of a maven artifact change selecting an older version
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DROOLS-906
>                 URL: https://issues.jboss.org/browse/DROOLS-906
>             Project: Drools
>          Issue Type: Bug
>    Affects Versions: 6.2.0.Final
>         Environment: Ear containing a startup bean, with the kiescanner loaded at postconstruct,
> deployed in Wildfly 8.2.0 
>            Reporter: Getano Piazzolla
>            Assignee: Mario Fusco
>            Priority: Critical
>              Labels: drools, kie, maven
>
> When using the KieScanner as indicated in the guide, if the kContainer is initalized using a ReleaseIdImpl that idicate
> as version "RELEASE", the KieScanner do not find changes in the repository if we indicate as RELEASE a previous version of the repository.
> IN CODE:
> ReleaseIdImpl releaseId = new ReleaseIdImpl("blabla", "blabla", "RELEASE");
> KieServices ks = KieServices.Factory.get();
> kContainer = ks.newKieContainer(releaseId);
> kieScanner = ks.newKieScanner(kContainer);
> kieScanner.start(5000L);
> For example if we change the maven-metadata.xml/maven-metadata-local.xml 
> FROM
> <metadata>
>   <groupId>com.noemalife.dmcs.rules</groupId>
>   <artifactId>maven-validation-rules</artifactId>
>   <versioning>
>     <release>0.2</release>
>     <versions>
>       <version>0.1</version>
>       <version>0.2</version>
>     </versions>
>     <lastUpdated></lastUpdated>
>   </versioning>
> </metadata>
> TO
> <metadata>
>   <groupId>com.noemalife.dmcs.rules</groupId>
>   <artifactId>maven-validation-rules</artifactId>
>   <versioning>
>     <release>0.1</release>
>     <versions>
>       <version>0.1</version>
>       <version>0.2</version>
>     </versions>
>     <lastUpdated></lastUpdated>
>   </versioning>
> </metadata>
> The kieScanner do not find changes; I have to restart the AS to be able to load the correct RELEASE version.
> (The kieScanner behaves and updates correctly if I change the release version from 0.1 to 0.2 )



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