[
https://issues.apache.org/jira/browse/BEAM-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17131985#comment-17131985
]
Beam JIRA Bot commented on BEAM-1976:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> Allow only one runner profile active at once in examples and archetypes
> -----------------------------------------------------------------------
>
> Key: BEAM-1976
> URL: https://issues.apache.org/jira/browse/BEAM-1976
> Project: Beam
> Issue Type: Sub-task
> Components: examples-java
> Reporter: Aviem Zur
> Priority: P2
> Labels: stale-P2
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
