Make the REST/Webapps dependency sets more maintainable

XMLWordPrintable

    • Type: Task
    • Resolution: Unresolved
    • Priority: L3 - Default
    • None
    • Affects Version/s: None
    • Component/s: run
    • None

      Problem
      Currently, the camunda-bpm-run-modules and camunda-bpm-run-ee-modules define a set of dependencies as provided so they are not provided to the final distribution ZIP as a dependency set because the Spring Boot App ZIP already includes them. This is quite hard to be maintained because it needs to be checked to include all artifacts that are already part of the Spring Boot App ZIP. Also, this needs to be duplicated in CE and EE.

      Possible Solution

      1. Pull in all dependencies for the modules REST and Webapps (might even happen in the assembly.xml already instead of in separate modules)
      2. Either use a filtering mechanism Maven provides or create a post-build-script that removes all artifacts from the dependency sets that are already part of the Spring Boot App ZIP

        This is the controller panel for Smart Panels app

              Assignee:
              Unassigned
              Reporter:
              Tobias Metzke-Bernstein
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: