Recommend loading as an external exporter via the JAR path for Zeebe 1.0.1 #188
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR updates the QA tests and the documentation to make it explicit that the recommended way of loading the exporter is as an external JAR (e.g. using the
jarPath
configuration option) that is not located in thelib/
folder of the Zeebe broker. This will avoid hard to diagnose issues which may stem from unpredictable dependency version conflicts.Pull Request Checklist
mvn clean install -DskipTests
locally before committing