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

Make project work with assertj 2 and 3

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • assert-3.0.0
    • None
    • assert
    • None

      Options:

      1. A single artifact that is compatible with both versions
      2. Multiple artifacts, depending on assertj version, either with classifier or a different artifact id

      Decide if assertj should be a in provided or compile dependency scope

        This is the controller panel for Smart Panels app

            [CAM-9794] Make project work with assertj 2 and 3

            Tobias Metzke-Bernstein added a comment - - edited
            1. Single artifact that works with both versions AND multiple JDK versions is not possible (as far as I tried)
            2. Three artifacts: camunda-bpm-assert, camunda-bpm-assert-assertj2 and camunda-bpm-assert-assertj3-9-1
            3. camunda-bpm-assert compiled against 3.11.1 with JDK 1.8 (uses specific API calls, can ONLY be used with JDK 1.8+ and provided assertj 3.x)
            4. camunda-bpm-assert-assertj2 is a "compatibility artifact", could be removed when we drop support for JDK 1.7, but doesn't have to be (can be used with any JDK 1.7+, can ONLY be used with provided assertj 2.x)
            5. camunda-bpm-assert-assertj3-9-1 is a "compatibility artifact", could be removed when we move to bpm-platform 7.11 (can ONLY be used with provided assertj 3.9.1 that comes with spring-boot 2.0.x)
            6. provided scope to let library users decide which specific version they need/want/already use

            Tobias Metzke-Bernstein added a comment - - edited Single artifact that works with both versions AND multiple JDK versions is not possible (as far as I tried) Three artifacts: camunda-bpm-assert, camunda-bpm-assert-assertj2 and camunda-bpm-assert-assertj3-9-1 camunda-bpm-assert compiled against 3.11.1 with JDK 1.8 (uses specific API calls, can ONLY be used with JDK 1.8+ and provided assertj 3.x) camunda-bpm-assert-assertj2 is a "compatibility artifact", could be removed when we drop support for JDK 1.7, but doesn't have to be (can be used with any JDK 1.7+, can ONLY be used with provided assertj 2.x) camunda-bpm-assert-assertj3-9-1 is a "compatibility artifact", could be removed when we move to bpm-platform 7.11 (can ONLY be used with provided assertj 3.9.1 that comes with spring-boot 2.0.x) provided scope to let library users decide which specific version they need/want/already use

              nikola.koevski Nikola Koevski
              thorben.lindhauer Thorben Lindhauer
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: