[
https://issues.apache.org/jira/browse/CALCITE-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148963#comment-15148963
]
Julian Hyde edited comment on CALCITE-553 at 2/16/16 5:38 PM:
--------------------------------------------------------------
Reviewing https://github.com/apache/calcite/pull/196:
* Is the {{!}} part of the property name? Or is there a maven convention I'm
not aware of. Seems that it might fall afoul of some shells.
* How about having a property called 'generate' or 'skipGenerate' that controls
both generations?
* Can you add an example of its usage to howto.md.
was (Author: julianhyde):
Reviewing https://github.com/apache/calcite/pull/196:
* Is the '!' part of the property name? Or is there a maven convention I'm not
aware of. Seems that '!' might fall afoul of some shells.
* How about having a property called 'generate' or 'skipGenerate' that controls
both generations?
* Can you add an example of its usage to howto.md.
> "mvn clean install" fails due to missing SqlParserImpl
> ------------------------------------------------------
>
> Key: CALCITE-553
> URL: https://issues.apache.org/jira/browse/CALCITE-553
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Josh Elser
> Fix For: next
>
>
> Every second time I call {mvn -DskipTests clean install} it fails with
> {code}[ERROR] COMPILATION ERROR :
> [INFO] -------------------------------------------------------------
> [ERROR]
> /home/jhyde/open1/calcite.2/core/src/main/java/org/apache/calcite/sql/parser/SqlParser.java:[24,42]
> cannot find symbol
> symbol: class SqlParserImpl
> location: package org.apache.calcite.sql.parser.impl
> [ERROR]
> /home/jhyde/open1/calcite.2/core/src/main/java/org/apache/calcite/sql/parser/SqlParser.java:[201,50]
> cannot find symbol
> symbol: variable SqlParserImpl
> location: class org.apache.calcite.sql.parser.SqlParser.ConfigBuilder
> [INFO] 2 errors{code}
> I think CALCITE-484 broke something; maybe the parser is not generated
> correctly if at the start of the mvn command (before clean) the parser
> already exists.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)