Uploaded image for project: 'JBoss BPMS Platform'
  1. JBoss BPMS Platform
  2. RHBPMS-4403

Dependency validation issues after upgrading from BxMS 6.1 to 6.3.3

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 6.4.0
    • 6.3.3.GA
    • Business Central
    • None

    • Upgrading projects from BPM Suite 6.1.x to BPM Suite 6.3.3;

    • CR1
    • Workaround Exists
    • Hide

      The workaround is to set manually the "All packages included" to Package White List... but it is only feasible if there are just a few projects. It is very laborious for customers who have a lot of projects and dependencies.

      Show
      The workaround is to set manually the "All packages included" to Package White List... but it is only feasible if there are just a few projects. It is very laborious for customers who have a lot of projects and dependencies.
    • Hide

      1) Create a project in BPM Suite 6.1.x;
      2) Add an external dependency (Artifact Repository);
      3) Add it as a project dependency in "Dependendecies list" page from the project;
      4) Create a rule and use the data model in the condition, save;

      5) Clone this repository to BPM Suite 6.3.3 and upload the same Artifact Repository;
      6) Going to dependencies list page, you will be able to see the dependency, but after opening the rule it throws a validation error.

      Note: you can simply clone to BPM Suite 6.3.3 the project attached (xxx) as I created it on BPM Suite 6.1.x in order to ease the test. The main goal is to show that by default the dependencies can not be resolved after the upgrade.

      Show
      1) Create a project in BPM Suite 6.1.x; 2) Add an external dependency (Artifact Repository); 3) Add it as a project dependency in "Dependendecies list" page from the project; 4) Create a rule and use the data model in the condition, save; 5) Clone this repository to BPM Suite 6.3.3 and upload the same Artifact Repository; 6) Going to dependencies list page, you will be able to see the dependency, but after opening the rule it throws a validation error. Note: you can simply clone to BPM Suite 6.3.3 the project attached (xxx) as I created it on BPM Suite 6.1.x in order to ease the test. The main goal is to show that by default the dependencies can not be resolved after the upgrade.

    Description

      After upgrading from 6.1.x to 6.3.3 some dependency issues have been happening.

      All dependencies added to the projects can be seen from Open Project Editor -> Dependencies list page, but it is set to Packages not included by default for all projects.

      The issue is gone after changing from Packages not included to All Packages Included for Package White List under Dependencies page.

      It seems to be a regression issue since the same projects worked well in BxMS 6.1, and now it seems like it is a requirement to add the packages to the "packages-name-white-list" file.

      Note: It needs to be tested on BPM Suite 6.3.3 since 6.3.1, 6.3.2 have a bug[1] that does not display dependencies.

      [1] https://issues.jboss.org/browse/RHBPMS-3997

      Attachments

        1. newRepo.zip
          84 kB
        2. reproducer.zip
          94 kB

        Activity

          People

            trikkola Toni Rikkola
            rhn-support-ajuricic Amana Juricic
            Jan Hrcek Jan Hrcek (Inactive)
            Jan Hrcek Jan Hrcek (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: