[jira] [Comment Edited] (FLINK-2858) Cannot build Flink Scala 2.11 with IntelliJ
[ https://issues.apache.org/jira/browse/FLINK-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14958887#comment-14958887 ] Robert Metzger edited comment on FLINK-2858 at 10/15/15 1:26 PM: - tl;dr: This issue is due to a missing feature in IntelliJ (mvn itself is powerful enough to work properly) The problem is that we're Flink is using the "scala-2.11" property to activate and deactivate the scala-2.10 and scala-2.11 profiles. In flink-scala/pom.xml there is a scala-2.10 profile which activates itself even if the scala-2.11 profile is selected in IntelliJ. I am not aware of a way of setting maven properties in IntelliJ. I think [~aalexandrov] did it like this because we need to remove a dependency (scala macros) for scala-2.11. We can probably also activate the profile with the regular profile activation and activate the scala-2.10 profile with "activateByDefault". was (Author: rmetzger): The problem is that we're Flink is using the "scala-2.11" property to activate and deactivate the scala-2.10 and scala-2.11 profiles. In flink-scala/pom.xml there is a scala-2.10 profile which activates itself even if the scala-2.11 profile is selected in IntelliJ. I am not aware of a way of setting maven properties in IntelliJ. I think [~aalexandrov] did it like this because we need to remove a dependency (scala macros) for scala-2.11. We can probably also activate the profile with the regular profile activation and activate the scala-2.10 profile with "activateByDefault". > 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)
[jira] [Comment Edited] (FLINK-2858) Cannot build Flink Scala 2.11 with IntelliJ
[ https://issues.apache.org/jira/browse/FLINK-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14959689#comment-14959689 ] Alexander Alexandrov edited comment on FLINK-2858 at 10/15/15 10:29 PM: [~trohrm...@apache.org] After trying around for a while I managed to overcome the issue. Here are the required steps * Run the `tools/change-scala-version.sh` script * Run `mvn clean` from the console * Optionally, forcefully activate the `scala-2.11` profile & deactivate `scala-2.10` from the IntelliJ Maven panel. Strictly speeking this is not needed because after running the script the default profile is changed to `scala-2.11`. * In IntelliJ, click "Generate Sources and Update Folders for all Projects" in the same panel (but maybe a simple "Reimport all Maven projects" will be enough) * In IntelliJ, run "Build > Rebuild Project" This worked for me on the latest IntelliJ Ultimate (14.1.5). was (Author: aalexandrov): [~trohrm...@apache.org] After trying around for a while I managed to overcome the issue. Here are the steps * Run the `tools/change-scala-version.sh` script * Run `mvn clean` from the console * Optionally, forcefully activate the `scala-2.11` profile & deactivate `scala-2.10` from the IntelliJ Maven panel. Strictly speeking this is not needed because after running the script the default profile is changed to `scala-2.11`. * In IntelliJ, click "Generate Sources and Update Folders for all Projects" in the same panel (but maybe a simple "Reimport all Maven projects" will be enough) * In IntelliJ, run "Build > Rebuild Project" This worked for me on the latest IntelliJ Ultimate (14.1.5). > 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)
[jira] [Comment Edited] (FLINK-2858) Cannot build Flink Scala 2.11 with IntelliJ
[ https://issues.apache.org/jira/browse/FLINK-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14959689#comment-14959689 ] Alexander Alexandrov edited comment on FLINK-2858 at 10/15/15 10:28 PM: [~trohrm...@apache.org] After trying around for a big I managed to overcome the issue. Here are the steps * Run the `tools/change-scala-version.sh` script * Run `mvn clean` from the console * Optionally, forcefully activate the `scala-2.11` profile & deactivate `scala-2.10` from the IntelliJ Maven panel. Strictly speeking this is not needed because after running the script the default profile is changed to `scala-2.11`. * In IntelliJ, click "Generate Sources and Update Folders for all Projects" in the same panel (but maybe a simple "Reimport all Maven projects" will be enough) * In IntelliJ, run "Build > Rebuild Project" This worked for me on the latest IntelliJ Ultimate (14.1.5). was (Author: aalexandrov): [~trohrm...@apache.org] After trying around for a big I managed to overcome the issue. Here are the steps * Run the `tools/change-scala-version.sh` script * Run `mvn clean` from the console * Optionally, forcefully activate the `scala-2.11` profile & deactivate `scala-2.10` from the IntelliJ Maven panel. Strictly speeking this is not needed because after running the script the default profile is changed to `scala-2.11`. * Click "Generate Sources and Update Folders for all Projects" in the same panel (but maybe a simple "Reimport all Maven projects" will be enough) * Run "Build > Rebuild Project" This worked for me on the latest IntelliJ Ultimate (14.1.5). > 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)
[jira] [Comment Edited] (FLINK-2858) Cannot build Flink Scala 2.11 with IntelliJ
[ https://issues.apache.org/jira/browse/FLINK-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14959689#comment-14959689 ] Alexander Alexandrov edited comment on FLINK-2858 at 10/15/15 10:27 PM: [~trohrm...@apache.org] After trying around for a big I managed to overcome the issue. Here are the steps * Run the `tools/change-scala-version.sh` script * Run `mvn clean` from the console * Optionally, forcefully activate the `scala-2.11` profile & deactivate `scala-2.10` from the IntelliJ Maven panel. Strictly speeking this is not needed because after running the script the default profile is changed to `scala-2.11`. * Click "Generate Sources and Update Folders for all Projects" in the same panel (but maybe a simple "Reimport all Maven projects" will be enough) * Run "Build > Rebuild Project" This worked for me on the latest IntelliJ Ultimate (14.1.5). was (Author: aalexandrov): [~trohrm...@apache.org] After trying around for a big I managed to overcome the issue. Here are the steps * Run the `tools/change-scala-version.sh` script * Run `mvn clean` from the console * Activate the `scala-2.11` profile & deactivate `scala-2.10` from the IntelliJ Maven panel * Click "Generate Sources and Update Folders for all Projects" in the same panel (but maybe a simple "Reimport all Maven projects" will be enough) * Run "Build > Rebuild Project" This worked for me on the latest IntelliJ Ultimate (14.1.5). > 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)
[jira] [Comment Edited] (FLINK-2858) Cannot build Flink Scala 2.11 with IntelliJ
[
https://issues.apache.org/jira/browse/FLINK-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14959689#comment-14959689
]
Alexander Alexandrov edited comment on FLINK-2858 at 10/15/15 10:30 PM:
[~trohrm...@apache.org] After trying around for a while I managed to overcome
the issue. Here are the required steps
* Run the {{tools/change-scala-version.sh}} script
* Run {{mvn clean}} from the console
* Optionally, forcefully activate the {{scala-2.11}} profile & deactivate
{{scala-2.10}} from the IntelliJ Maven panel. Strictly speeking this is not
needed because after running the script the default profile is changed to
{{scala-2.11}}.
* In IntelliJ, click "Generate Sources and Update Folders for all Projects" in
the same panel (but maybe a simple "Reimport all Maven projects" will be enough)
* In IntelliJ, run "Build > Rebuild Project"
This worked for me on the latest IntelliJ Ultimate (14.1.5).
was (Author: aalexandrov):
[~trohrm...@apache.org] After trying around for a while I managed to overcome
the issue. Here are the required steps
* Run the `tools/change-scala-version.sh` script
* Run `mvn clean` from the console
* Optionally, forcefully activate the `scala-2.11` profile & deactivate
`scala-2.10` from the IntelliJ Maven panel. Strictly speeking this is not
needed because after running the script the default profile is changed to
`scala-2.11`.
* In IntelliJ, click "Generate Sources and Update Folders for all Projects" in
the same panel (but maybe a simple "Reimport all Maven projects" will be enough)
* In IntelliJ, run "Build > Rebuild Project"
This worked for me on the latest IntelliJ Ultimate (14.1.5).
> 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)
[jira] [Comment Edited] (FLINK-2858) Cannot build Flink Scala 2.11 with IntelliJ
[ https://issues.apache.org/jira/browse/FLINK-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14959689#comment-14959689 ] Alexander Alexandrov edited comment on FLINK-2858 at 10/15/15 10:29 PM: [~trohrm...@apache.org] After trying around for a while I managed to overcome the issue. Here are the steps * Run the `tools/change-scala-version.sh` script * Run `mvn clean` from the console * Optionally, forcefully activate the `scala-2.11` profile & deactivate `scala-2.10` from the IntelliJ Maven panel. Strictly speeking this is not needed because after running the script the default profile is changed to `scala-2.11`. * In IntelliJ, click "Generate Sources and Update Folders for all Projects" in the same panel (but maybe a simple "Reimport all Maven projects" will be enough) * In IntelliJ, run "Build > Rebuild Project" This worked for me on the latest IntelliJ Ultimate (14.1.5). was (Author: aalexandrov): [~trohrm...@apache.org] After trying around for a big I managed to overcome the issue. Here are the steps * Run the `tools/change-scala-version.sh` script * Run `mvn clean` from the console * Optionally, forcefully activate the `scala-2.11` profile & deactivate `scala-2.10` from the IntelliJ Maven panel. Strictly speeking this is not needed because after running the script the default profile is changed to `scala-2.11`. * In IntelliJ, click "Generate Sources and Update Folders for all Projects" in the same panel (but maybe a simple "Reimport all Maven projects" will be enough) * In IntelliJ, run "Build > Rebuild Project" This worked for me on the latest IntelliJ Ultimate (14.1.5). > 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)
