[ https://issues.apache.org/jira/browse/FLINK-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14959761#comment-14959761 ]
Alexander Alexandrov commented on FLINK-2858: --------------------------------------------- I think that it also makes sense to place a comment on the scala-2.11 profiles which indicate that these are not meant to be overridden by the user. We can also try to pull the {{scala.binary.version}} property out to the general {{properties}} section and rework the profiles so they activate themselves based on the current {{scala.binary.version}} value, but AFAIR [~rmetzger] mentioned once that property-based activation is not really supported by Maven at the moment. > Cannot build Flink Scala 2.11 with IntelliJ > ------------------------------------------- > > Key: FLINK-2858 > URL: https://issues.apache.org/jira/browse/FLINK-2858 > Project: Flink > Issue Type: Bug > Components: Build System > Affects Versions: 0.10 > Reporter: Till Rohrmann > > If I activate the scala-2.11 profile from within IntelliJ (and thus > deactivate the scala-2.10 profile) in order to build Flink with Scala 2.11, > then Flink cannot be built. The problem is that some Scala macros cannot be > expanded because they were compiled with the wrong version (I assume 2.10). > This makes debugging tests with Scala 2.11 in IntelliJ impossible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)