geode-issues mailing list archives

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

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

Mark Bretl commented on GEODE-42:
---------------------------------

So I think the issue you brought up initially was that a developer can't build outside of
an SCM environment if we only have the GIT commands. I will create a new patch which will
check the existence of a .git directory and if it not available, then it will take default
values. I think this will be the best approach until we get farther into the source distribution
discussion.

> 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