You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2016/11/30 09:20:58 UTC
[jira] [Updated] (CALCITE-1516) Upgrade
hydromatic-resource-maven-plugin, and re-work SaffronProperties
[ https://issues.apache.org/jira/browse/CALCITE-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Hyde updated CALCITE-1516:
---------------------------------
Description:
Upgrade {{hydromatic-resource-maven-plugin}} to version 0.6, and use its [new ability to wrap properties files|https://github.com/julianhyde/hydromatic-resource/issues/6] to re-work {{SaffronProperties}}.
{{SaffronProperties}} becomes an interface and all of its metadata (e.g. the type, path and default value of each property) is represented in Java annotations.
This will allow us to obsolete the {{eigenbase-properties}} library.
If this is successful we could use a similar approach for {{CalciteConnectionConfig}}.
was:
Upgrade `hydromatic-resource-maven-plugin` to version 0.6, and use its [new ability to wrap properties files|https://github.com/julianhyde/hydromatic-resource/issues/6] to re-work `SaffronProperties`.
`SaffronProperties` becomes an interface and all of its metadata (e.g. the type, path and default value of each property) is represented in Java annotations.
If this is successful we could use a similar approach for `CalciteConnectionConfig`.
> Upgrade hydromatic-resource-maven-plugin, and re-work SaffronProperties
> -----------------------------------------------------------------------
>
> Key: CALCITE-1516
> URL: https://issues.apache.org/jira/browse/CALCITE-1516
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Julian Hyde
>
> Upgrade {{hydromatic-resource-maven-plugin}} to version 0.6, and use its [new ability to wrap properties files|https://github.com/julianhyde/hydromatic-resource/issues/6] to re-work {{SaffronProperties}}.
> {{SaffronProperties}} becomes an interface and all of its metadata (e.g. the type, path and default value of each property) is represented in Java annotations.
> This will allow us to obsolete the {{eigenbase-properties}} library.
> If this is successful we could use a similar approach for {{CalciteConnectionConfig}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)