[jboss-jira] [JBoss JIRA] (DROOLS-5180) Kie-scanner update container API doesn't refresh container with latest jar after new year

[Mario Fusco (Jira)]

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

Mario Fusco resolved DROOLS-5180.
---------------------------------
    Resolution: Explained


Your versioning scheme breaks the lexicographic order. To clarify, in your example the version number

{code}
10.23.2019-06-30-00
{code}

comes lexicographically AFTER than 

{code}
04.02.2020-15-00-04
{code}

and that's why maven (and then the kie-server) doesn't recognize the second as a newer version. If you want to use the date as version number use the format YYYY.MM.DD instead of the current DD.MM.YYYY and this should fix the problem.

> Kie-scanner update container API doesn't refresh container with latest jar after new year
> -----------------------------------------------------------------------------------------
>
>                 Key: DROOLS-5180
>                 URL: https://issues.redhat.com/browse/DROOLS-5180
>             Project: Drools
>          Issue Type: Bug
>          Components: core engine
>    Affects Versions: 7.18.0.Final
>            Reporter: Minal Bhalodi
>            Assignee: Mario Fusco
>            Priority: Critical
>
> We are using kie-server as a stand alone application. we use kie scanner to update kie container when there is a new DRL file in our .m2 folder. 
> we don't have scanner polling but we use Scanner update container API to update kie container.
> Every year when date changes after new year, we are facing issue where kie scanner is not able to update container with latest jar in m2 with new year date. 
> When we check the container version it shows latest with new year date but internally kie is still using old jar.
> We fixed this issue with create container API instead update container.
> kie-server-spring-boot-starter-drools :7.18.0.Final
> Please let me know if this issue is already fixed or discussed before or if you need more details.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)