You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Anthony Baker (JIRA)" <ji...@apache.org> on 2016/01/08 04:59:40 UTC

[jira] [Updated] (GEODE-42) Remove hard-coded SCM metadata from build

     [ https://issues.apache.org/jira/browse/GEODE-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anthony Baker updated GEODE-42:
-------------------------------
    Affects Version/s:     (was: 1.0.0-incubating)
                       1.0.0-alpha1

> Remove hard-coded SCM metadata from build
> -----------------------------------------
>
>                 Key: GEODE-42
>                 URL: https://issues.apache.org/jira/browse/GEODE-42
>             Project: Geode
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 1.0.0-alpha1
>            Reporter: Anthony Baker
>            Assignee: Mark Bretl
>            Priority: Minor
>             Fix For: 1.0.0-alpha1
>
>         Attachments: GEODE-42-1.patch, GEODE-42-2.patch
>
>
> In gemfire-core/build.gradle the createVersionPropertiesFile task uses hard-coded source information:
> {code}
>     ext.gitBranch = 'master'
>     ext.commitId = '1366ff2d4fcbf54bfad684e9ba9822db2a2b0ff5'
>     ext.sourceDate = '2015-04-06 14:54:51 -0700'
> {code}
> Previously this information was obtained from SCM (e.g. invoking the git command directly).  However, we will be releasing src tarballs and need to build from source without access to SCM metadata.



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