You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Dmitry Orlovsky (Jira)" <ji...@apache.org> on 2022/03/04 21:30:00 UTC

[jira] [Created] (BEAM-14051) There should be single source of truth for the project version

Dmitry Orlovsky created BEAM-14051:
--------------------------------------

             Summary: There should be single source of truth for the project version
                 Key: BEAM-14051
                 URL: https://issues.apache.org/jira/browse/BEAM-14051
             Project: Beam
          Issue Type: Wish
          Components: build-system
            Reporter: Dmitry Orlovsky


Now the Beam version is defined in two places:
 * via the 'version' parameter [in gradle.properties|https://github.com/apache/beam/blob/master/gradle.properties#L27],
 * programmatically in the `apply` function [in BeamModulePlugin|[https://github.com/apache/beam/blob/master/buildSrc/src/main/groovy/org/apache/beam/gradle/BeamModulePlugin.groovy#L384-L387].]

The latter effectively overrides the former. For someone not very familiar with the Beam build system this may result in a hard to understand and debug behavior: unexpected version gets build and/or pushed to local Maven repository, and changing version in `gradle.properties` does not have any effect.

Adding a comment with a reference to `BeamModulePlugin` to `gradle.properties` can be a good start, and in the long run it would be great to have single source of truth for the project version.

 

 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)