Details
-
Task
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
3
-
S
Description
Context:
In the following PR https://github.com/camunda/camunda-optimize/pull/4278#discussion_r782443483 semver4j was introduced for convenience on version comparison in contrast to extending own version check logic further.
To be consistent we should make use of it in other occasions (e.g. camunda BPM and elastic version checkers) as well.
AT:
- semver4j is used to get rid of custom version comparison code for elastic and camunda bpm version checks
Justification:
The consistent logic for checking reduces potential error-proneness in our own custom logic. It is also a duplication of similar checks, which is a redundancy in our codebase