[jira] [Comment Edited] (CALCITE-994) Calcite development under Eclipse IDE

["Alexander Reshetov (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CALCITE-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15041218#comment-15041218 ] 

Alexander Reshetov edited comment on CALCITE-994 at 12/4/15 7:36 AM:
---------------------------------------------------------------------

Didn't investigate the root of issues with Checkstyle yet.

But I suppose Java Build Path issue caused by this:

Top-level pom.xml requires Java 1.7 (through maven-compiler-plugin).
Also some modules requires even earlier version:
- calcite-mongodb - 1.5
- calcite-plus - 1.5
- calcite-spark - 1.5
- calcite-ubenchmark - 1.6

So the question is that specific versions really needed or it just hasn't been updated for a while?

If they needed - then this JDK versions should be presented on development machine.
If not - pom.xml files should be updated to use current JDK 1.8



----



And here is quick and dirty workaround. Use it only if you really need to start working right now.

Two actions used below:
- Set correct JRE Library
  In project/module properties go to Java Build Path  - Libraries
  Edit JRE System Library and set it to JavaSE-1.8
  Apply
- Disable Checkstyle
  In project/module properties go to Checkstyle - Main
  Uncheck "Checkstyle active for this project"
  OK

After project import open module (Eclipse's project) properties for each module (listed below)

apply next actions
- Set correct JRE Library
- Disable Checkstyle

to modules/projects:
- calcite-avatica
- calcite-avatica-server
- calcite-core
- calcite-example-csv
- calcite-example-function
- calcite-linq4j
- calcite-mongodb
- calcite-piglet
- calcite-plus
- calcite-spark
- calcite-splunk
- calcite-ubenchmark




was (Author: areshetov):
Didn't investigate the root of issues with Checkstyle yet.

But I suppose Java Build Path issue caused by this:

Top-level pom.xml requires Java 1.7 (through maven-compiler-plugin).
Also some modules requires even earlier version:
- calcite-mongodb - 1.5
- calcite-plus - 1.5
- calcite-spark - 1.5
- calcite-ubenchmark - 1.6

So the question is that specific versions really needed or it just hasn't been updated for a while?

If they needed - then this JDK versions should be presented on development machine.
If not - pom.xml files should be updated to use current JDK 1.8



----



And here is quick and dirty workaround. Use it only if you really need to start working right now.

Two actions used below:
- Set correct JRE Library
  In project/module properties go to Java Build Path  - Libraries
  Edit JRE System Library and set it to JavaSE-1.8
  Apply
- Disable Checkstyle
  In project/module properties go to Checkstyle - Main
  Uncheck "Checkstyle active for this project"
  OK

After project import open module (Eclipse's project) properties for each module (listed below) apply next actions
- Set correct JRE Library
- Disable Checkstyle
to modules/projects:
- calcite-avatica
- calcite-avatica-server
- calcite-core
- calcite-example-csv
- calcite-example-function
- calcite-linq4j
- calcite-mongodb
- calcite-piglet
- calcite-plus
- calcite-spark
- calcite-splunk
- calcite-ubenchmark



> Calcite development under Eclipse IDE
> -------------------------------------
>
>                 Key: CALCITE-994
>                 URL: https://issues.apache.org/jira/browse/CALCITE-994
>             Project: Calcite
>          Issue Type: Improvement
>          Components: site
>            Reporter: Alexander Reshetov
>            Assignee: Julian Hyde
>            Priority: Minor
>         Attachments: lifecycle-mapping-metadata.xml
>
>
> After "git clone" project could not be imported in Eclipse as existing Maven project.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)