You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Frances Perry (JIRA)" <ji...@apache.org> on 2017/08/11 20:35:00 UTC
[jira] [Assigned] (BEAM-1976) Allow only one runner profile active
at once in examples and archetypes
[ https://issues.apache.org/jira/browse/BEAM-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Frances Perry reassigned BEAM-1976:
-----------------------------------
Assignee: (was: Frances Perry)
> 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
>
> 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
(v6.4.14#64029)