Uploaded image for project: 'Drools'
  1. Drools
  2. DROOLS-906

Kiescanner do not find updates in the KieContainer if the current RELEASE of a maven artifact change selecting an older version

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Critical
    • None
    • 6.2.0.Final
    • None
    • Workaround Exists
    • Hide

      This is not a workaround but a way to avoid the USE this functionality and bypass the bug.

      We can deploy in to the repository a new RELEASE [indicating it as a new version] but instead is the older one that we want to use.

      Show
      This is not a workaround but a way to avoid the USE this functionality and bypass the bug. We can deploy in to the repository a new RELEASE [indicating it as a new version] but instead is the older one that we want to use.
    • Low
    • NEW
    • NEW

    Description

      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 )

      Attachments

        Activity

          People

            mfusco@redhat.com Mario Fusco
            gpiazzolla Getano Piazzolla (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: