Re: Review Request 54616: GEODE-2098 Document that gfsh history is in .geode dir

2016-12-10 Thread Avinash Dongre 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/54616/#review158754
---


Ship it!




Ship It!

- Avinash Dongre


On Dec. 10, 2016, 12:17 a.m., Karen Miller wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/54616/
> ---
> 
> (Updated Dec. 10, 2016, 12:17 a.m.)
> 
> 
> Review request for geode, Dave Barnes and Joey McAllister.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> GEODE-2098 Document that gfsh history is in .geode dir
> 
> 
> Diffs
> -
> 
>   geode-docs/tools_modules/gfsh/command-pages/history.html.md.erb 
> 04e47366ad24341ec8831fe681b8f170d50e4c34 
> 
> Diff: https://reviews.apache.org/r/54616/diff/
> 
> 
> Testing
> ---
> 
> gradle rat check passes
> 
> Book builds with no broken links.
> 
> 
> Thanks,
> 
> Karen Miller
> 
>

Build failed in Jenkins: Geode-nightly #680

2016-12-10 Thread Apache Jenkins Server 
See 

Changes:

[adongre] GEODE-1984: Fix Issue Make GatewaySender destroy a public API

[adongre] GEODE-1984: Addressed review comments, Removed copy pasted repeating

[jiliao] [GEODE-2196] Add test for Cluster Config. Refactor

[upthewaterspout] GEODE-2186: Changing the gateway status to only looking 
running status

[abaker] Update website release references to remove incubator

[bschuchardt] GEODE-2193 a member is kicked out immediately after joining

--
[...truncated 1616 lines...]
:geode-cq:compileTestJavaNote: Some input files use or override a deprecated 
API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

:geode-cq:processTestResources
:geode-cq:testClasses
:geode-cq:checkMissedTests
:geode-cq:spotlessJavaCheck
:geode-cq:spotlessCheck
:geode-cq:test
:geode-cq:check
:geode-cq:build
:geode-cq:distributedTest
:geode-cq:flakyTest
:geode-cq:integrationTest
:geode-json:assemble
:geode-json:compileTestJava UP-TO-DATE
:geode-json:processTestResources UP-TO-DATE
:geode-json:testClasses UP-TO-DATE
:geode-json:checkMissedTests UP-TO-DATE
:geode-json:spotlessJavaCheck
:geode-json:spotlessCheck
:geode-json:test UP-TO-DATE
:geode-json:check
:geode-json:build
:geode-json:distributedTest UP-TO-DATE
:geode-json:flakyTest UP-TO-DATE
:geode-json:integrationTest UP-TO-DATE
:geode-junit:javadoc
:geode-junit:javadocJar
:geode-junit:sourcesJar
:geode-junit:signArchives SKIPPED
:geode-junit:assemble
:geode-junit:compileTestJava
:geode-junit:processTestResources UP-TO-DATE
:geode-junit:testClasses
:geode-junit:checkMissedTests
:geode-junit:spotlessJavaCheck
:geode-junit:spotlessCheck
:geode-junit:test
:geode-junit:check
:geode-junit:build
:geode-junit:distributedTest
:geode-junit:flakyTest
:geode-junit:integrationTest
:geode-lucene:assemble
:geode-lucene:compileTestJavaNote: Some input files use or override a 
deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

:geode-lucene:processTestResources
:geode-lucene:testClasses
:geode-lucene:checkMissedTests
:geode-lucene:spotlessJavaCheck
:geode-lucene:spotlessCheck
:geode-lucene:test
:geode-lucene:check
:geode-lucene:build
:geode-lucene:distributedTest
:geode-lucene:flakyTest
:geode-lucene:integrationTest
:geode-old-client-support:assemble
:geode-old-client-support:compileTestJava
:geode-old-client-support:processTestResources UP-TO-DATE
:geode-old-client-support:testClasses
:geode-old-client-support:checkMissedTests
:geode-old-client-support:spotlessJavaCheck
:geode-old-client-support:spotlessCheck
:geode-old-client-support:test
:geode-old-client-support:check
:geode-old-client-support:build
:geode-old-client-support:distributedTest
:geode-old-client-support:flakyTest
:geode-old-client-support:integrationTest
:geode-pulse:assemble
:geode-pulse:compileTestJavaNote: 

 uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

:geode-pulse:processTestResources
:geode-pulse:testClasses
:geode-pulse:checkMissedTests
:geode-pulse:spotlessJavaCheck
:geode-pulse:spotlessCheck
:geode-pulse:test
:geode-pulse:check
:geode-pulse:build
:geode-pulse:distributedTest
:geode-pulse:flakyTest
:geode-pulse:integrationTest
:geode-rebalancer:assemble
:geode-rebalancer:compileTestJava
:geode-rebalancer:processTestResources UP-TO-DATE
:geode-rebalancer:testClasses
:geode-rebalancer:checkMissedTests
:geode-rebalancer:spotlessJavaCheck
:geode-rebalancer:spotlessCheck
:geode-rebalancer:test
:geode-rebalancer:check
:geode-rebalancer:build
:geode-rebalancer:distributedTest
:geode-rebalancer:flakyTest
:geode-rebalancer:integrationTest
:geode-wan:assemble
:geode-wan:compileTestJavaNote: Some input files use or override a deprecated 
API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

:geode-wan:processTestResources
:geode-wan:testClasses
:geode-wan:checkMissedTests
:geode-wan:spotlessJavaCheck
:geode-wan:spotlessCheck
:geode-wan:test
:geode-wan:check
:geode-wan:build
:geode-wan:distributedTest
:geode-wan:flakyTest
:geode-wan:integrationTest
:geode-web:assemble
:geode-web:compileTestJavaNote: Some input files use or override a deprecated 
API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

:geode-web:processTestResources UP-TO-DATE
:geode-web:testClasses
:geode-web:checkMissedTe

[jira] [Created] (GEODE-2203) gfsh status locator/server - Give more descriptive output on empty parameter

2016-12-10 Thread Alyssa Kim (JIRA) 
Alyssa Kim created GEODE-2203:
-

 Summary: gfsh status locator/server - Give more descriptive output 
on empty parameter
 Key: GEODE-2203
 URL: https://issues.apache.org/jira/browse/GEODE-2203
 Project: Geode
  Issue Type: Improvement
  Components: gfsh
Reporter: Alyssa Kim
Assignee: Mark Bretl


Currently, executing some status commands in gfsh without valid parameters 
gives a vague explanation/output that might be misleading. Although we have 
help  for usage description, displaying 'null' as an output might 
not be the best idea.

Current Result
{code}
gfsh>status locator
null
{code}

{code}
gfsh>status server
Server in 
C:\Users\XXX\git\incubator-geode\geode-assembly\build\install\apache-geode\bin 
on null is currently not responding.
{code}

Improvement
{code}
gfsh>status locator
SYNTAX
status locator [--name=value] [--host=value] [--port=value] [--pid=value]
Use help status locator to display detailed usage information
{code}

{code}
gfsh>status server
SYNTAX
status server [--name=value] [--pid=value] [--dir=value]
Use help status server to display detailed usage information
{code}



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

[jira] [Updated] (GEODE-2203) gfsh status locator/server - Give more descriptive output on empty parameter

2016-12-10 Thread Alyssa Kim (JIRA) 

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

Alyssa Kim updated GEODE-2203:
--
Priority: Minor  (was: Major)

> gfsh status locator/server - Give more descriptive output on empty parameter
> 
>
> Key: GEODE-2203
> URL: https://issues.apache.org/jira/browse/GEODE-2203
> Project: Geode
>  Issue Type: Improvement
>  Components: gfsh
>Reporter: Alyssa Kim
>Assignee: Mark Bretl
>Priority: Minor
>
> Currently, executing some status commands in gfsh without valid parameters 
> gives a vague explanation/output that might be misleading. Although we have 
> help  for usage description, displaying 'null' as an output 
> might not be the best idea.
> Current Result
> {code}
> gfsh>status locator
> null
> {code}
> {code}
> gfsh>status server
> Server in 
> C:\Users\XXX\git\incubator-geode\geode-assembly\build\install\apache-geode\bin
>  on null is currently not responding.
> {code}
> Improvement
> {code}
> gfsh>status locator
> SYNTAX
> status locator [--name=value] [--host=value] [--port=value] [--pid=value]
> Use help status locator to display detailed usage information
> {code}
> {code}
> gfsh>status server
> SYNTAX
> status server [--name=value] [--pid=value] [--dir=value]
> Use help status server to display detailed usage information
> {code}



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

[jira] [Commented] (GEODE-2203) gfsh status locator/server - Give more descriptive output on empty parameter

2016-12-10 Thread Alyssa Kim (JIRA) 

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

Alyssa Kim commented on GEODE-2203:
---

Please assign this back to me after the review. Since this issue is not major, 
I'd like to work on this jira (not sure why I can't assign it to myself though).

> gfsh status locator/server - Give more descriptive output on empty parameter
> 
>
> Key: GEODE-2203
> URL: https://issues.apache.org/jira/browse/GEODE-2203
> Project: Geode
>  Issue Type: Improvement
>  Components: gfsh
>Reporter: Alyssa Kim
>Assignee: Mark Bretl
>Priority: Minor
>
> Currently, executing some status commands in gfsh without valid parameters 
> gives a vague explanation/output that might be misleading. Although we have 
> help  for usage description, displaying 'null' as an output 
> might not be the best idea.
> Current Result
> {code}
> gfsh>status locator
> null
> {code}
> {code}
> gfsh>status server
> Server in 
> C:\Users\XXX\git\incubator-geode\geode-assembly\build\install\apache-geode\bin
>  on null is currently not responding.
> {code}
> Improvement
> {code}
> gfsh>status locator
> SYNTAX
> status locator [--name=value] [--host=value] [--port=value] [--pid=value]
> Use help status locator to display detailed usage information
> {code}
> {code}
> gfsh>status server
> SYNTAX
> status server [--name=value] [--pid=value] [--dir=value]
> Use help status server to display detailed usage information
> {code}



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

[jira] [Commented] (GEODE-2203) gfsh status locator/server - Give more descriptive output on empty parameter

2016-12-10 Thread Kirk Lund (JIRA) 

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

Kirk Lund commented on GEODE-2203:
--

[~dalyssakim] For some reason I'm unable to assign this to you as well -- I'm 
guessing it's related to permissions but I'll try to find out on Monday.

For the Geode1.0 release we removed geode-joptsimple module which was a fork of 
jopt-simple. GFSH was using this fork to perform validation of command 
arguments. When we switched to a dependency on a regular binary release of 
jopt-simple, we lost that detailed validation. The code in GFSH that used the 
old geode-joptsimple is still there and all of the GFSH code needs quite a bit 
of cleanup. [~jinmeiliao] has a branch where she's replacing the use of 
jopt-simple with using just spring shell for parsing -- this might be something 
to keep in mind or you might even want to checkout her branch.

> gfsh status locator/server - Give more descriptive output on empty parameter
> 
>
> Key: GEODE-2203
> URL: https://issues.apache.org/jira/browse/GEODE-2203
> Project: Geode
>  Issue Type: Improvement
>  Components: gfsh
>Reporter: Alyssa Kim
>Assignee: Mark Bretl
>Priority: Minor
>
> Currently, executing some status commands in gfsh without valid parameters 
> gives a vague explanation/output that might be misleading. Although we have 
> help  for usage description, displaying 'null' as an output 
> might not be the best idea.
> Current Result
> {code}
> gfsh>status locator
> null
> {code}
> {code}
> gfsh>status server
> Server in 
> C:\Users\XXX\git\incubator-geode\geode-assembly\build\install\apache-geode\bin
>  on null is currently not responding.
> {code}
> Improvement
> {code}
> gfsh>status locator
> SYNTAX
> status locator [--name=value] [--host=value] [--port=value] [--pid=value]
> Use help status locator to display detailed usage information
> {code}
> {code}
> gfsh>status server
> SYNTAX
> status server [--name=value] [--pid=value] [--dir=value]
> Use help status server to display detailed usage information
> {code}



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

Assigning Jira tickets to new contributors

2016-12-10 Thread Kirk Lund 
Does anyone know what needs to be done to enable assigning a Jira ticket to
a new contributor? Alyssa Kim filed GEODE-2203 and would like to have the
ticket assigned to her but Jira shows either "No Matches" or "User 'Alyssa
Kim' does not exist." -- her user id on the Apache Jira is dalyssakim.

Thanks,
Kirk

Re: Assigning Jira tickets to new contributors

2016-12-10 Thread Deepak Dixit 
Hello Kirk,

I remember some apache help document mentioning need for user to be added
to the project group.
May be adding user to GEODE project group will help in enabling them to
assign issues to themselves.

Can you please grant similar permission to me (details are added below) so
I can assign JIRA issue I am working on?
I am currently working on GEODE-2109 and just finished with GEODE-734.

Detail for apache id
Email ID: deepakdixit2...@gmail.com
apache id: deepakddixit

Thanks,

Deepak


On Dec 11, 2016 9:41 AM, "Kirk Lund"  wrote:

Does anyone know what needs to be done to enable assigning a Jira ticket to
a new contributor? Alyssa Kim filed GEODE-2203 and would like to have the
ticket assigned to her but Jira shows either "No Matches" or "User 'Alyssa
Kim' does not exist." -- her user id on the Apache Jira is dalyssakim.

Thanks,
Kirk