[
https://issues.apache.org/jira/browse/BAHIR-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764522#comment-16764522
]
ASF GitHub Bot commented on BAHIR-193:
--------------------------------------
lresende commented on issue #43: BAHIR-193: facilitate scala version change
URL: https://github.com/apache/bahir-flink/pull/43#issuecomment-462163044
With your proposed change, how do you build different versions of Scala?
Also, for a downstream consumer, how will it use 2.11 versus 2.12 version of a
dependency if both will point to ONE parent pom that has ONE definition of
scala.binary.version ?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> changes so scala version modifications are easier
> -------------------------------------------------
>
> Key: BAHIR-193
> URL: https://issues.apache.org/jira/browse/BAHIR-193
> Project: Bahir
> Issue Type: Improvement
> Components: Flink Streaming Connectors
> Reporter: Joao Boto
> Assignee: Joao Boto
> Priority: Major
>
> remove scala version from artifact name on parent
> on modules set scala version by parameter with ${scala.binary.version}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
