geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anthony Baker (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-42) Remove hard-coded SCM metadata from build
Date Wed, 03 Jun 2015 02:22:49 GMT

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

Anthony Baker commented on GEODE-42:
------------------------------------

Good suggestion, I agree!

> 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-incubating
>            Reporter: Anthony Baker
>            Assignee: Mark Bretl
>            Priority: Minor
>         Attachments: GEODE-42-1.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)

Mime
View raw message