Allow only one runner profile active at once in examples and archetypes
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 196
Description
Since only one SLF4J logger binding is allowed in the classpath, we shouldn't allow more than one runner profile to be active at once in our examples/archetype modules since different runners use different bindings.
Also, remove slf4j-jdk14 dependency from root and place it instead in direct-runner and dataflow-runner profiles, for the same reason.
Imported from Jira [BEAM-1976](https://issues.apache.org/jira/browse/BEAM-1976). Original Jira may contain additional context.
Reported by: aviemzur.
Subtask of issue #18244
Contributor guide
Research direction
Start by inspecting the Maven profile definitions in the examples and archetype modules, then locate the root slf4j-jdk14 dependency and the direct-runner and dataflow-runner profiles. Done means the profiles prevent multiple runner profiles from being active together and slf4j-jdk14 is scoped only to the two specified runner profiles.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100