You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2021/10/21 08:55:00 UTC

[jira] [Created] (FLINK-24609) flink-rpc-akka uses wrong Scala version property for parser-combinators

Chesnay Schepler created FLINK-24609:
----------------------------------------

             Summary: flink-rpc-akka uses wrong Scala version property for parser-combinators
                 Key: FLINK-24609
                 URL: https://issues.apache.org/jira/browse/FLINK-24609
             Project: Flink
          Issue Type: Bug
          Components: Build System
    Affects Versions: 1.14.0, 1.15.0
            Reporter: Chesnay Schepler
            Assignee: Chesnay Schepler
             Fix For: 1.15.0, 1.14.1


dependencyManagement entry:
{code}
<dependency>
	<groupId>org.scala-lang.modules</groupId>
	<artifactId>scala-parser-combinators_${scala.binary.version}</artifactId>
	<version>1.1.2</version>
</dependency>
{code}

Conceptually this should use {{${akka.scala.binary.version}}}.

Interestingly enough, changing this breaks the build because maven then ignores the entry entirely, only using the existing entry from the root pom. I think there's some bug where if properties are used in artifactIds, then the properties references themselves must match in order to override them. Amazingly, this even fails if you hard-code the scala version.

Adding a direct dependency on parser-combinators does fix the packaging problem, but then we run into dependency convergence errors.
What we can try is overriding {{scala.binary.version}} instead; maybe that does the trick...




--
This message was sent by Atlassian Jira
(v8.3.4#803005)