[
https://issues.apache.org/jira/browse/FLINK-7032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16067894#comment-16067894
]
ASF GitHub Bot commented on FLINK-7032:
---------------------------------------
Github user pnowojski commented on the issue:
https://github.com/apache/flink/pull/4213
Yes. Should I not do this?
> Intellij is constantly changing language level of sub projects back to 1.6
> ---------------------------------------------------------------------------
>
> Key: FLINK-7032
> URL: https://issues.apache.org/jira/browse/FLINK-7032
> Project: Flink
> Issue Type: Improvement
> Reporter: Piotr Nowojski
> Assignee: Piotr Nowojski
>
> Every time I do maven reimport projects, Intellij is switching back to 1.6
> language level. I tracked down this issue to misconfiguration in our pom.xml
> file. It correctly configure maven-compiler-plugin:
> {code:xml}
> <plugin>
> <!-- just define the Java version to be used
> for compiling and plugins -->
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-compiler-plugin</artifactId>
> <version>3.1</version><!--$NO-MVN-MAN-VER$-->
> <configuration>
> <source>${java.version}</source>
> <target>${java.version}</target>
> <!-- The output of Xlint is not shown
> by default, but we activate it for the QA bot
> to be able to get more warnings -->
>
> <compilerArgument>-Xlint:all</compilerArgument>
> </configuration>
> </plugin>
> {code}
> where ${java.version} is set to 1.7 in the properties, but it forgets to
> overwrite the following properties from apache-18.pom:
> {code:xml}
> <properties>
> <maven.compiler.source>1.6</maven.compiler.source>
> <maven.compiler.target>1.6</maven.compiler.target>
> </properties>
> {code}
> It seems like compiling from console using maven ignores those values, but
> they are confusing Intellij.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
