Skip to content

[SPARK-21605][BUILD] Let IntelliJ IDEA correctly detect Language level and Target byte code version#18808

Closed
baibaichen wants to merge 1 commit intoapache:masterfrom
baibaichen:feature/idea-fix
Closed

[SPARK-21605][BUILD] Let IntelliJ IDEA correctly detect Language level and Target byte code version#18808
baibaichen wants to merge 1 commit intoapache:masterfrom
baibaichen:feature/idea-fix

Conversation

@baibaichen
Copy link
Contributor

With SPARK-21592, removing source and target properties from maven-compiler-plugin lets IntelliJ IDEA use default Language level and Target byte code version which are 1.4.

This change adds source, target and encoding properties back to fix this issue. As I test, it doesn't increase compile time.

@baibaichen
Copy link
Contributor Author

cc @gslowikowski , @srowen

@viirya
Copy link
Member

viirya commented Aug 2, 2017

This may need a JIRA to track it.

@baibaichen baibaichen changed the title [HOT-FIX][BUILD] Let IntelliJ IDEA correctly detect Language level and Target byte code version [SPARK-21605][HOT-FIX][BUILD] Let IntelliJ IDEA correctly detect Language level and Target byte code version Aug 2, 2017
@baibaichen
Copy link
Contributor Author

https://issues.apache.org/jira/browse/SPARK-21605 is added

@gslowikowski
Copy link
Contributor

I removed too much in #18750. Eclipse uses these two configuration parameters of maven-compiler-plugin too.

@wangyum
Copy link
Member

wangyum commented Aug 2, 2017

Jenkins, test this please

Copy link
Member

@srowen srowen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. It's not really a hot-fix though. Is encoding needed?

@baibaichen baibaichen changed the title [SPARK-21605][HOT-FIX][BUILD] Let IntelliJ IDEA correctly detect Language level and Target byte code version [SPARK-21605][BUILD] Let IntelliJ IDEA correctly detect Language level and Target byte code version Aug 2, 2017
…l and Target byte code version

With SPARK-21592, removing source and target properties from maven-compiler-plugin lets IntelliJ IDEA use default Language level and Target byte code version which are 1.4.

This change adds source, target and encoding properties back to fix this issues.  As I test, it doesn't increase compile time.
@baibaichen
Copy link
Contributor Author

baibaichen commented Aug 2, 2017

@srowen

  1. just remove hotfix from title
  2. encoding is unnecessary, since its default value is ${project.build.sourceEncoding} which is UTF-8.

@baibaichen
Copy link
Contributor Author

Jenkins, test this please

@viirya
Copy link
Member

viirya commented Aug 2, 2017

We may need a committer to trigger the jenkins.

@SparkQA
Copy link

SparkQA commented Aug 2, 2017

Test build #3870 has finished for PR 18808 at commit d690a03.

  • This patch fails PySpark unit tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@SparkQA
Copy link

SparkQA commented Aug 2, 2017

Test build #3871 has finished for PR 18808 at commit d690a03.

  • This patch fails SparkR unit tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@SparkQA
Copy link

SparkQA commented Aug 2, 2017

Test build #3873 has started for PR 18808 at commit d690a03.

@gatorsmile
Copy link
Member

I hit the same issue! Thanks for fixing it!

@SparkQA
Copy link

SparkQA commented Aug 3, 2017

Test build #3874 has finished for PR 18808 at commit d690a03.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@asfgit asfgit closed this in e7c59b4 Aug 3, 2017
@baibaichen baibaichen deleted the feature/idea-fix branch August 4, 2017 01:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants

Comments