[
https://issues.apache.org/jira/browse/BEAM-6799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Luckey updated BEAM-6799:
---------------------------------
Description:
Currently we have project version set in gradle.properties [1]. On the other
hand we overwrite immediately the project version in BeamModulePlugin [2], so
that the usage in gradle.properties is superfluous.
This is intermingled with isRelease flag, which toggles version as snapshot
version. Revisit that procedure and make consistent.
See also BEAM-6726 (comments about removing isRelease) and BEAM-6798 about
usage of version in gradle.properties.
was:
Currently we have project version set in gradle.properties [1]. On the other
hand we overwrite immediately the project version in BeamModulePlugin [2], so
that the usage in gradle.properties superfluous.
This is intermingled with isRelease flag, which toggles version as snapshot
version. Revisit that procedure and make consistent.
See also BEAM-6726 (comments about removing isRelease) and BEAM-6798 about
usage of version in gradle.properties.
> Streamline project version usage
> --------------------------------
>
> Key: BEAM-6799
> URL: https://issues.apache.org/jira/browse/BEAM-6799
> Project: Beam
> Issue Type: Improvement
> Components: build-system
> Reporter: Michael Luckey
> Priority: Major
>
> Currently we have project version set in gradle.properties [1]. On the other
> hand we overwrite immediately the project version in BeamModulePlugin [2], so
> that the usage in gradle.properties is superfluous.
> This is intermingled with isRelease flag, which toggles version as snapshot
> version. Revisit that procedure and make consistent.
> See also BEAM-6726 (comments about removing isRelease) and BEAM-6798 about
> usage of version in gradle.properties.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
