[jira] [Commented] (GEODE-3199) geode-examples on the release branch prompts for a gpg password

2017-10-30 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-3199:


Commit 76cce858773dd390c27de717a5d7c92a9d7aaf9b in geode-examples's branch 
refs/heads/master from [~upthewaterspout]
[ https://gitbox.apache.org/repos/asf?p=geode-examples.git;h=76cce85 ]

GEODE-3199: Make signing with a gpg key optional

Make it optional to sign the archives with a gpg key, to avoid annoying
users trying to build the examples. You must specify the property
-PsignArchives to sign with a gpg key.


> geode-examples on the release branch prompts for a gpg password
> ---
>
> Key: GEODE-3199
> URL: https://issues.apache.org/jira/browse/GEODE-3199
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: Dan Smith
> Fix For: 1.3.0, 1.2.1
>
>
> When building geode-examples using ./gradlew build from the release/1.2.0 
> branch, I get prompted to enter my gpg password. Since our instructions on 
> running the examples tell the user to run gradlew build, they will hit this 
> prompt when building the released examples.
> Travis is also showing this failure:
> https://travis-ci.org/apache/geode-examples/builds/244002605
> {noformat}
> You must configure your signing.keyId and signing.secretKeyRingFile
> in ~/.gradle/gradle.properties in order to sign jars
> See https://cwiki.apache.org/confluence/display/GEODE/Release+Steps
> FAILURE: Build failed with an exception.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (GEODE-3199) geode-examples on the release branch prompts for a gpg password

2017-09-20 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-3199:


Commit 5d034de588a43cdefb8fbb3a6259579785768340 in geode-examples's branch 
refs/heads/develop from [~upthewaterspout]
[ https://gitbox.apache.org/repos/asf?p=geode-examples.git;h=5d034de ]

GEODE-3199: Make signing with a gpg key optional

Make it optional to sign the archives with a gpg key, to avoid annoying
users trying to build the examples. You must specify the property
-PsignArchives to sign with a gpg key.

(cherry picked from commit 76cce858773dd390c27de717a5d7c92a9d7aaf9b)


> geode-examples on the release branch prompts for a gpg password
> ---
>
> Key: GEODE-3199
> URL: https://issues.apache.org/jira/browse/GEODE-3199
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: Dan Smith
> Fix For: 1.3.0, 1.2.1
>
>
> When building geode-examples using ./gradlew build from the release/1.2.0 
> branch, I get prompted to enter my gpg password. Since our instructions on 
> running the examples tell the user to run gradlew build, they will hit this 
> prompt when building the released examples.
> Travis is also showing this failure:
> https://travis-ci.org/apache/geode-examples/builds/244002605
> {noformat}
> You must configure your signing.keyId and signing.secretKeyRingFile
> in ~/.gradle/gradle.properties in order to sign jars
> See https://cwiki.apache.org/confluence/display/GEODE/Release+Steps
> FAILURE: Build failed with an exception.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (GEODE-3199) geode-examples on the release branch prompts for a gpg password

2017-09-20 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-3199:


Commit 5d034de588a43cdefb8fbb3a6259579785768340 in geode-examples's branch 
refs/heads/master from [~upthewaterspout]
[ https://gitbox.apache.org/repos/asf?p=geode-examples.git;h=5d034de ]

GEODE-3199: Make signing with a gpg key optional

Make it optional to sign the archives with a gpg key, to avoid annoying
users trying to build the examples. You must specify the property
-PsignArchives to sign with a gpg key.

(cherry picked from commit 76cce858773dd390c27de717a5d7c92a9d7aaf9b)


> geode-examples on the release branch prompts for a gpg password
> ---
>
> Key: GEODE-3199
> URL: https://issues.apache.org/jira/browse/GEODE-3199
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: Dan Smith
> Fix For: 1.3.0, 1.2.1
>
>
> When building geode-examples using ./gradlew build from the release/1.2.0 
> branch, I get prompted to enter my gpg password. Since our instructions on 
> running the examples tell the user to run gradlew build, they will hit this 
> prompt when building the released examples.
> Travis is also showing this failure:
> https://travis-ci.org/apache/geode-examples/builds/244002605
> {noformat}
> You must configure your signing.keyId and signing.secretKeyRingFile
> in ~/.gradle/gradle.properties in order to sign jars
> See https://cwiki.apache.org/confluence/display/GEODE/Release+Steps
> FAILURE: Build failed with an exception.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (GEODE-3199) geode-examples on the release branch prompts for a gpg password

2017-07-20 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-3199:


Commit 5d034de588a43cdefb8fbb3a6259579785768340 in geode-examples's branch 
refs/heads/release/1.2.1 from [~upthewaterspout]
[ https://git-wip-us.apache.org/repos/asf?p=geode-examples.git;h=5d034de ]

GEODE-3199: Make signing with a gpg key optional

Make it optional to sign the archives with a gpg key, to avoid annoying
users trying to build the examples. You must specify the property
-PsignArchives to sign with a gpg key.

(cherry picked from commit 76cce858773dd390c27de717a5d7c92a9d7aaf9b)


> geode-examples on the release branch prompts for a gpg password
> ---
>
> Key: GEODE-3199
> URL: https://issues.apache.org/jira/browse/GEODE-3199
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: Dan Smith
> Fix For: 1.3.0, 1.2.1
>
>
> When building geode-examples using ./gradlew build from the release/1.2.0 
> branch, I get prompted to enter my gpg password. Since our instructions on 
> running the examples tell the user to run gradlew build, they will hit this 
> prompt when building the released examples.
> Travis is also showing this failure:
> https://travis-ci.org/apache/geode-examples/builds/244002605
> {noformat}
> You must configure your signing.keyId and signing.secretKeyRingFile
> in ~/.gradle/gradle.properties in order to sign jars
> See https://cwiki.apache.org/confluence/display/GEODE/Release+Steps
> FAILURE: Build failed with an exception.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (GEODE-3199) geode-examples on the release branch prompts for a gpg password

2017-07-19 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-3199:


Commit 76cce858773dd390c27de717a5d7c92a9d7aaf9b in geode-examples's branch 
refs/heads/develop from [~upthewaterspout]
[ https://git-wip-us.apache.org/repos/asf?p=geode-examples.git;h=76cce85 ]

GEODE-3199: Make signing with a gpg key optional

Make it optional to sign the archives with a gpg key, to avoid annoying
users trying to build the examples. You must specify the property
-PsignArchives to sign with a gpg key.


> geode-examples on the release branch prompts for a gpg password
> ---
>
> Key: GEODE-3199
> URL: https://issues.apache.org/jira/browse/GEODE-3199
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: Dan Smith
> Fix For: 1.3.0, 1.2.1
>
>
> When building geode-examples using ./gradlew build from the release/1.2.0 
> branch, I get prompted to enter my gpg password. Since our instructions on 
> running the examples tell the user to run gradlew build, they will hit this 
> prompt when building the released examples.
> Travis is also showing this failure:
> https://travis-ci.org/apache/geode-examples/builds/244002605
> {noformat}
> You must configure your signing.keyId and signing.secretKeyRingFile
> in ~/.gradle/gradle.properties in order to sign jars
> See https://cwiki.apache.org/confluence/display/GEODE/Release+Steps
> FAILURE: Build failed with an exception.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (GEODE-3199) geode-examples on the release branch prompts for a gpg password

2017-07-17 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on GEODE-3199:
---

Github user asfgit closed the pull request at:

https://github.com/apache/geode-examples/pull/9


> geode-examples on the release branch prompts for a gpg password
> ---
>
> Key: GEODE-3199
> URL: https://issues.apache.org/jira/browse/GEODE-3199
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: Dan Smith
>
> When building geode-examples using ./gradlew build from the release/1.2.0 
> branch, I get prompted to enter my gpg password. Since our instructions on 
> running the examples tell the user to run gradlew build, they will hit this 
> prompt when building the released examples.
> Travis is also showing this failure:
> https://travis-ci.org/apache/geode-examples/builds/244002605
> {noformat}
> You must configure your signing.keyId and signing.secretKeyRingFile
> in ~/.gradle/gradle.properties in order to sign jars
> See https://cwiki.apache.org/confluence/display/GEODE/Release+Steps
> FAILURE: Build failed with an exception.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (GEODE-3199) geode-examples on the release branch prompts for a gpg password

2017-07-12 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on GEODE-3199:
---

Github user upthewaterspout commented on the issue:

https://github.com/apache/geode-examples/pull/9
  
@metatype - I updated the PR. Travis is now stuck on find a 1.2 geode 
distribution, but it got past the signing check.


> geode-examples on the release branch prompts for a gpg password
> ---
>
> Key: GEODE-3199
> URL: https://issues.apache.org/jira/browse/GEODE-3199
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: Dan Smith
>
> When building geode-examples using ./gradlew build from the release/1.2.0 
> branch, I get prompted to enter my gpg password. Since our instructions on 
> running the examples tell the user to run gradlew build, they will hit this 
> prompt when building the released examples.
> Travis is also showing this failure:
> https://travis-ci.org/apache/geode-examples/builds/244002605
> {noformat}
> You must configure your signing.keyId and signing.secretKeyRingFile
> in ~/.gradle/gradle.properties in order to sign jars
> See https://cwiki.apache.org/confluence/display/GEODE/Release+Steps
> FAILURE: Build failed with an exception.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (GEODE-3199) geode-examples on the release branch prompts for a gpg password

2017-07-12 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on GEODE-3199:
---

GitHub user upthewaterspout opened a pull request:

https://github.com/apache/geode-examples/pull/9

GEODE-3199: Make signing with a gpg key optional

Make it optional to sign the archives with a gpg key, to avoid annoying
users trying to build the examples.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/upthewaterspout/geode-examples 
feature/GEODE-3199

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/geode-examples/pull/9.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #9


commit c6b110abece7b0801054e8f44b0f430155391e90
Author: Dan Smith 
Date:   2017-07-12T22:30:13Z

GEODE-3199: Make signing with a gpg key optional

Make it optional to sign the archives with a gpg key, to avoid annoying
users trying to build the examples.




> geode-examples on the release branch prompts for a gpg password
> ---
>
> Key: GEODE-3199
> URL: https://issues.apache.org/jira/browse/GEODE-3199
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: Dan Smith
>
> When building geode-examples using ./gradlew build from the release/1.2.0 
> branch, I get prompted to enter my gpg password. Since our instructions on 
> running the examples tell the user to run gradlew build, they will hit this 
> prompt when building the released examples.
> Travis is also showing this failure:
> https://travis-ci.org/apache/geode-examples/builds/244002605
> {noformat}
> You must configure your signing.keyId and signing.secretKeyRingFile
> in ~/.gradle/gradle.properties in order to sign jars
> See https://cwiki.apache.org/confluence/display/GEODE/Release+Steps
> FAILURE: Build failed with an exception.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)