[jira] [Commented] (CALCITE-539) Avoid org-apache-calcite-jdbc.properties being regenerated on each compilation

["Julian Hyde (JIRA)" <ji...@apache.org>]

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

Julian Hyde commented on CALCITE-539:
-------------------------------------

Could we create it only if it does not exist? For regular builds we would get a stale build.timestamp -- but that's not a problem. For release builds we would be sure to do a clean first, therefore we will get an accurate build.timestamp.

> Avoid org-apache-calcite-jdbc.properties being regenerated on each compilation
> ------------------------------------------------------------------------------
>
>                 Key: CALCITE-539
>                 URL: https://issues.apache.org/jira/browse/CALCITE-539
>             Project: Calcite
>          Issue Type: Sub-task
>    Affects Versions: 1.0.0-incubating
>            Reporter: Vladimir Sitnikov
>            Assignee: Julian Hyde
>
> org-apache-calcite-jdbc.properties includes {{build.timestamp=$\{build.timestamp\}}} so it is different on each build execution.
> Need to do something with that.
> Does it make sense to convert this file to some generated java source?
> That might allow us to reuse Velocity caching of maven-remote-resource-plugins.



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