Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-7116

[Designer] Work item definition deployments on wrong path

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.12.0.Final
    • 7.9.0.Final
    • Designer
    • None
    • 2
    • NEW
    • NEW
    • 2018 Week 36-38

    Description

      The jbpm-designer actually performs the work item definitions deployments for:

      1. Some default items (eg: Email, Log)
      2. The remote items from a service task repository, if specified the given JVM system properties for it

      And the target paths for the deployments are:

      1. Default items into "<project_root>/global"
      2. Remote items into "<project_root>/<proj_name>/src/main/resources/<whatever_pkg>"

      The bug is on the target path for the deployment of remote items (2). The <proj_name> just after the <proj_root> must not be there. It does not match the guvnor project/package default/expected structure.

      Example: Importing remote work items into a project named "p1" results into the assets created in "p1/src/main/resources/com/myteam/p1", instead of the resources excepted root at "src/main/resources/com/myteam/p1"

      This bug affect the co-existence between both designers (Stunner), as Stunner does the deployment of the remote work items into the path provided by the Project guvnor model, which results in the default resources root for the project. But as the designer checks another root, it also deploys again the remote work items definitions in a different path.

      Attachments

        Issue Links

          Activity

            People

              rhn-support-tsurdilo Tihomir Surdilovic (Inactive)
              romartin@redhat.com Roger Martinez
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: