Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-4406

Spike: Split up JobDSL jobs and utils

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Duplicate
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • continuous integration
    • None

      Maybe it is reasonable and better to separate the actual job descriptions from the groovy utils we use to build them. Currently we port changes to various branches if add/fix a generator or add a repository etc.

      Repositories
      1. Camunda JobDSL Utils: everything under src/ currently (only one master branch)
      2. Camunda JobDSL: the jobs/ and view/ directories (branches for different camunda versions)

      I'm not sure how to best handle the dependency. I think releases and gradle dependecy is just to much. Maybe git submodule or better subtree is the way to go.

        This is the controller panel for Smart Panels app

              Unassigned Unassigned
              sebastian.menski Sebastian Menski
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: