Jenkins build is back to normal : Geode-nightly #353

2016-01-21 Thread Apache Jenkins Server
See 



[GitHub] incubator-geode pull request: GEODE-749: refactor the code to look...

2016-01-21 Thread jdeppe-pivotal
Github user jdeppe-pivotal commented on the pull request:

https://github.com/apache/incubator-geode/pull/73#issuecomment-173606150
  
+1


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


Review Request 42576: unit test DisconnectingOutOfOffHeapMemoryListener

2016-01-21 Thread Darrel Schneider

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

Review request for geode, Scott Jewell, Ken Howe, Sai Boorlagadda, and Swapnil 
Bawaskar.


Bugs: GEODE-814
https://issues.apache.org/jira/browse/GEODE-814


Repository: geode


Description
---

Added unit test for DisconnectingOutOfOffHeapMemoryListener.

InternalDistributedSystem is no longer final so that unit tests can mock it. 
The reason it was made final was because in an older version of the product 
this class did license checking and we wanted to prevent it from being 
subclassed.


Diffs
-

  
gemfire-core/src/main/java/com/gemstone/gemfire/distributed/internal/InternalDistributedSystem.java
 8f604b47a5e952ca62cbb2e7afece4750a7de0d3 
  
gemfire-core/src/main/java/com/gemstone/gemfire/internal/offheap/DisconnectingOutOfOffHeapMemoryListener.java
 PRE-CREATION 
  
gemfire-core/src/main/java/com/gemstone/gemfire/internal/offheap/OffHeapStorage.java
 c950134099ac58e6befeeb891a9cecc98a4d4f04 
  
gemfire-core/src/test/java/com/gemstone/gemfire/internal/offheap/DisconnectingOutOfOffHeapMemoryListenerTest.java
 PRE-CREATION 

Diff: https://reviews.apache.org/r/42576/diff/


Testing
---

DisconnectingOutOfOffHeapMemoryListenerJUnitTest


Thanks,

Darrel Schneider



Review Request 42604: Add custom annotations and rules for tests

2016-01-21 Thread Kirk Lund

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

Review request for geode, Jens Deppe and Jinmei Liao.


Bugs: GEODE-772
https://issues.apache.org/jira/browse/GEODE-772


Repository: geode


Description
---

GEODE-772: Add custom annotations and rules for tests

This adds in new classes of junit annotations and rules for geode tests. No 
existing code is modified in this change set.

This is a sub-task to merge changes incrementally from feature/GEODE-217.


Diffs
-

  
gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/ConditionalIgnore.java
 PRE-CREATION 
  
gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/IgnoreCondition.java
 PRE-CREATION 
  gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/IgnoreUntil.java 
PRE-CREATION 
  gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/Repeat.java 
PRE-CREATION 
  gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/Retry.java 
PRE-CREATION 
  
gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/ConditionalIgnoreRule.java
 PRE-CREATION 
  
gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/ExpectedTimeoutRule.java
 PRE-CREATION 
  
gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/IgnoreUntilRule.java
 PRE-CREATION 
  
gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/RepeatRule.java
 PRE-CREATION 
  
gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/RetryRule.java
 PRE-CREATION 
  
gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/SerializableExternalResource.java
 PRE-CREATION 
  
gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/SerializableRuleChain.java
 PRE-CREATION 
  
gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/SerializableTemporaryFolder.java
 PRE-CREATION 
  
gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/SerializableTestName.java
 PRE-CREATION 
  
gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/SerializableTestRule.java
 PRE-CREATION 
  
gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/SerializableTestWatcher.java
 PRE-CREATION 
  
gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/SerializableTimeout.java
 PRE-CREATION 
  
gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/examples/RepeatingTestCasesExampleTest.java
 PRE-CREATION 
  
gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/examples/RetryRuleExampleTest.java
 PRE-CREATION 
  
gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/tests/ExpectedTimeoutRuleTest.java
 PRE-CREATION 
  
gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/tests/IgnoreUntilRuleTest.java
 PRE-CREATION 
  
gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/tests/JUnitRuleTestSuite.java
 PRE-CREATION 
  
gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/tests/RepeatRuleTest.java
 PRE-CREATION 
  
gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/tests/RetryRuleGlobalWithErrorTest.java
 PRE-CREATION 
  
gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/tests/RetryRuleGlobalWithExceptionTest.java
 PRE-CREATION 
  
gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/tests/RetryRuleLocalWithErrorTest.java
 PRE-CREATION 
  
gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/tests/RetryRuleLocalWithExceptionTest.java
 PRE-CREATION 
  
gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/tests/RuleAndClassRuleTest.java
 PRE-CREATION 
  
gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/tests/TestRunner.java
 PRE-CREATION 
  
gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/support/DefaultIgnoreCondition.java
 PRE-CREATION 
  
gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/support/IgnoreConditionEvaluationException.java
 PRE-CREATION 

Diff: https://reviews.apache.org/r/42604/diff/


Testing
---

precheckin


Thanks,

Kirk Lund



Re: Client/Server?

2016-01-21 Thread Barry Oglesby
John,

You can use the ClientMembershipListener in the client like:

1. Register ClientMembershipListener before before initializing
the ClientCache. This will ensure that the client gets callbacks for
servers that connect when its pool is pre-filled with connections.
2. Initialize ClientCache
3. Wait for server to start
4. When notified, continue

In my test, I used a CountDownLatch known to both the TestClient and
ClientMembershipListener to wait and notify.

In my TestClient, I defined waitForServer (step 3) like:

private void waitForServer() throws InterruptedException {
  System.out.println("Waiting for server");
  this.latch.await();
  System.out.println("Done waiting for server");
}

In my ClientMembershipListener, I defined memberJoined (step 4) like:

public void memberJoined(ClientMembershipEvent event) {
  if (!event.isClient()) {
  this.latch.countDown();
  }
}

If I start the TestClient before the server starts, it waits in
waitForServer. Once the server starts, it gets notified and continues. If I
start the TestClient after the server starts, it just sails through the
waitForServer.


Barry Oglesby
GemFire Advanced Customer Engineering (ACE)
For immediate support please contact Pivotal Support at
http://support.pivotal.io/


On Wed, Jan 20, 2016 at 6:59 PM, John Blum  wrote:

> Hi Barry-
>
> Thank you for the quick response.
>
> In my test class, I only start one (standalone) server (i.e. no locators,
> no other servers, etc) during setup, and the client (test) connects
> directly to that server. Unfortunately, without explicit coordination, it
> is entirely possible that the client will start first and attempt to
> connect while performing a cache operation before the server is fully
> started/initialized (and technically listening for/accepting client
> connections).
>
> So, unless there is retry logic in the Pool to try and connect until X
> number of attempts at Y intervals has been made, I am not sure how the
> ClientMembershipListener will work in this case, especially since the
> client has not connected (to anything) yet.
>
>
> *1. How do you register a ClientMembershipListener on the client?*
>
> I see that it can be registered with the ClientMembership
> 
>  [0]
> class, but that appears to be a management component used on the server.
> However, based on the *Javadoc* description (for memberJoined(event)
> 
>  [1])...
>
> *"Invoked when a client has connected to this process or when this process
> has connected to a CacheServer."*
>
> It does imply the ClientMembershipListener can be registered and used on
> the client, assuming the 2nd reference to "this process" actually refers to
> the client.
>
>
> 2. Then, I was thinking, if a ClientMembershipListener can somehow be
> registered on the client (where?), that I could potentially implement
> memberJoined(event)
> 
>  to
> block any client cache operations (implemented in the test) until the
> client has actually connected.  I assume this is what you mean by...
>
> *"You could possibly use a ClientMembershipListener. If you install one in
> your client, the memberJoined callback will tell you when the client
> connects to the server."*
>
> However, I do not see where to register the ClientMembershipListener; the
> ClientCacheFactory nor the PoolFactory has any such API to perform the
> registration, and presumably, this would need to be done prior to
> connecting in order to receive the event when the client does, finally,
> successfully connect.
>
>
> 3. Or, I was also thinking, based on the "*How the Pool Connects to a
> Server*" section in the GemFire User Guide here
> ,
> that may also be feasible to use a combination of freeConnectionTimeout
> 
>  [2] with
> pingIntervals
> 
>  [3]
> (and perhaps, readTimeout
> 
>  [4])
> to del

[GitHub] incubator-geode pull request: GEODE-749: refactor the code to look...

2016-01-21 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/incubator-geode/pull/73


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


Re: Review Request 42604: Add custom annotations and rules for tests

2016-01-21 Thread Jinmei Liao

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

Ship it!


Ship It!

- Jinmei Liao


On Jan. 21, 2016, 6:03 p.m., Kirk Lund wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/42604/
> ---
> 
> (Updated Jan. 21, 2016, 6:03 p.m.)
> 
> 
> Review request for geode, Jens Deppe and Jinmei Liao.
> 
> 
> Bugs: GEODE-772
> https://issues.apache.org/jira/browse/GEODE-772
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> GEODE-772: Add custom annotations and rules for tests
> 
> This adds in new classes of junit annotations and rules for geode tests. No 
> existing code is modified in this change set.
> 
> This is a sub-task to merge changes incrementally from feature/GEODE-217.
> 
> 
> Diffs
> -
> 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/ConditionalIgnore.java
>  PRE-CREATION 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/IgnoreCondition.java
>  PRE-CREATION 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/IgnoreUntil.java 
> PRE-CREATION 
>   gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/Repeat.java 
> PRE-CREATION 
>   gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/Retry.java 
> PRE-CREATION 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/ConditionalIgnoreRule.java
>  PRE-CREATION 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/ExpectedTimeoutRule.java
>  PRE-CREATION 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/IgnoreUntilRule.java
>  PRE-CREATION 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/RepeatRule.java
>  PRE-CREATION 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/RetryRule.java
>  PRE-CREATION 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/SerializableExternalResource.java
>  PRE-CREATION 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/SerializableRuleChain.java
>  PRE-CREATION 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/SerializableTemporaryFolder.java
>  PRE-CREATION 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/SerializableTestName.java
>  PRE-CREATION 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/SerializableTestRule.java
>  PRE-CREATION 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/SerializableTestWatcher.java
>  PRE-CREATION 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/SerializableTimeout.java
>  PRE-CREATION 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/examples/RepeatingTestCasesExampleTest.java
>  PRE-CREATION 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/examples/RetryRuleExampleTest.java
>  PRE-CREATION 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/tests/ExpectedTimeoutRuleTest.java
>  PRE-CREATION 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/tests/IgnoreUntilRuleTest.java
>  PRE-CREATION 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/tests/JUnitRuleTestSuite.java
>  PRE-CREATION 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/tests/RepeatRuleTest.java
>  PRE-CREATION 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/tests/RetryRuleGlobalWithErrorTest.java
>  PRE-CREATION 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/tests/RetryRuleGlobalWithExceptionTest.java
>  PRE-CREATION 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/tests/RetryRuleLocalWithErrorTest.java
>  PRE-CREATION 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/tests/RetryRuleLocalWithExceptionTest.java
>  PRE-CREATION 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/tests/RuleAndClassRuleTest.java
>  PRE-CREATION 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/rules/tests/TestRunner.java
>  PRE-CREATION 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/support/DefaultIgnoreCondition.java
>  PRE-CREATION 
>   
> gemfire-junit/src/test/java/com/gemstone/gemfire/test/junit/support/IgnoreConditionEvaluationException.java
>  PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/42604/diff/
> 
> 
> Testing
> ---
> 
> precheckin
> 
> 
> Thanks,
> 
> Kirk Lund
> 
>



Re: Client/Server?

2016-01-21 Thread John Blum
Thanks Barry!

On Thu, Jan 21, 2016 at 10:13 AM, Barry Oglesby  wrote:

> John,
>
> You can use the ClientMembershipListener in the client like:
>
> 1. Register ClientMembershipListener before before initializing
> the ClientCache. This will ensure that the client gets callbacks for
> servers that connect when its pool is pre-filled with connections.
> 2. Initialize ClientCache
> 3. Wait for server to start
> 4. When notified, continue
>
> In my test, I used a CountDownLatch known to both the TestClient and
> ClientMembershipListener to wait and notify.
>
> In my TestClient, I defined waitForServer (step 3) like:
>
> private void waitForServer() throws InterruptedException {
>   System.out.println("Waiting for server");
>   this.latch.await();
>   System.out.println("Done waiting for server");
> }
>
> In my ClientMembershipListener, I defined memberJoined (step 4) like:
>
> public void memberJoined(ClientMembershipEvent event) {
>   if (!event.isClient()) {
>   this.latch.countDown();
>   }
> }
>
> If I start the TestClient before the server starts, it waits in
> waitForServer. Once the server starts, it gets notified and continues. If I
> start the TestClient after the server starts, it just sails through the
> waitForServer.
>
>
> Barry Oglesby
> GemFire Advanced Customer Engineering (ACE)
> For immediate support please contact Pivotal Support at
> http://support.pivotal.io/
>
>
> On Wed, Jan 20, 2016 at 6:59 PM, John Blum  wrote:
>
> > Hi Barry-
> >
> > Thank you for the quick response.
> >
> > In my test class, I only start one (standalone) server (i.e. no locators,
> > no other servers, etc) during setup, and the client (test) connects
> > directly to that server. Unfortunately, without explicit coordination, it
> > is entirely possible that the client will start first and attempt to
> > connect while performing a cache operation before the server is fully
> > started/initialized (and technically listening for/accepting client
> > connections).
> >
> > So, unless there is retry logic in the Pool to try and connect until X
> > number of attempts at Y intervals has been made, I am not sure how the
> > ClientMembershipListener will work in this case, especially since the
> > client has not connected (to anything) yet.
> >
> >
> > *1. How do you register a ClientMembershipListener on the client?*
> >
> > I see that it can be registered with the ClientMembership
> > <
> http://gemfire.docs.pivotal.io/docs-gemfire/latest/javadocs/japi/com/gemstone/gemfire/management/membership/ClientMembership.html#registerClientMembershipListener(com.gemstone.gemfire.management.membership.ClientMembershipListener)>
> [0]
> > class, but that appears to be a management component used on the server.
> > However, based on the *Javadoc* description (for memberJoined(event)
> > <
> http://gemfire.docs.pivotal.io/docs-gemfire/latest/javadocs/japi/com/gemstone/gemfire/management/membership/ClientMembershipListener.html#memberJoined(com.gemstone.gemfire.management.membership.ClientMembershipEvent)
> >
> >  [1])...
> >
> > *"Invoked when a client has connected to this process or when this
> process
> > has connected to a CacheServer."*
> >
> > It does imply the ClientMembershipListener can be registered and used on
> > the client, assuming the 2nd reference to "this process" actually refers
> to
> > the client.
> >
> >
> > 2. Then, I was thinking, if a ClientMembershipListener can somehow be
> > registered on the client (where?), that I could potentially implement
> > memberJoined(event)
> > <
> http://gemfire.docs.pivotal.io/docs-gemfire/latest/javadocs/japi/com/gemstone/gemfire/management/membership/ClientMembershipListener.html#memberJoined(com.gemstone.gemfire.management.membership.ClientMembershipEvent)>
> to
> > block any client cache operations (implemented in the test) until the
> > client has actually connected.  I assume this is what you mean by...
> >
> > *"You could possibly use a ClientMembershipListener. If you install one
> in
> > your client, the memberJoined callback will tell you when the client
> > connects to the server."*
> >
> > However, I do not see where to register the ClientMembershipListener; the
> > ClientCacheFactory nor the PoolFactory has any such API to perform the
> > registration, and presumably, this would need to be done prior to
> > connecting in order to receive the event when the client does, finally,
> > successfully connect.
> >
> >
> > 3. Or, I was also thinking, based on the "*How the Pool Connects to a
> > Server*" section in the GemFire User Guide here
> > <
> http://gemfire.docs.pivotal.io/docs-gemfire/latest/topologies_and_comm/topology_concepts/how_the_pool_manages_connections.html
> >,
> > that may also be feasible to use a combination of freeConnectionTimeout
> > <
> http://gemfire.docs.pivotal.io/docs-gemfire/latest/javadocs/japi/com/gemstone/gemfire/cache/client/PoolFactory.html#setFreeConnectionTimeout(int)>
> [2] with
> > pingIntervals
> > <
> http://gemfire.docs.pivotal.io/docs-

Re: Review Request 42561: Move dunit.standalone pkg to com.gemstone.gemfire.test.dunit.standalone

2016-01-21 Thread Dan Smith

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

Ship it!


Ship It!

- Dan Smith


On Jan. 21, 2016, 6:47 p.m., Kirk Lund wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/42561/
> ---
> 
> (Updated Jan. 21, 2016, 6:47 p.m.)
> 
> 
> Review request for geode, Jens Deppe, Jinmei Liao, and Dan Smith.
> 
> 
> Bugs: GEODE-715
> https://issues.apache.org/jira/browse/GEODE-715
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> GEODE-715: Move dunit.standalone pkg to 
> com.gemstone.gemfire.test.dunit.standalone
> 
> This is part of prepping for eventual repackaging to org.apache.geode. 
> GEODE-715 is one of the pieces of GEODE-217 (which has now been broken down 
> into multiple steps).
> 
> 
> Diffs
> -
> 
>   
> gemfire-core/src/test/java/com/gemstone/gemfire/internal/cache/PartitionedRegionDUnitTestCase.java
>  a4d32f2 
>   
> gemfire-core/src/test/java/com/gemstone/gemfire/internal/compression/CompressionRegionConfigDUnitTest.java
>  af7d07f 
>   
> gemfire-core/src/test/java/com/gemstone/gemfire/test/dunit/standalone/BounceResult.java
>  PRE-CREATION 
>   
> gemfire-core/src/test/java/com/gemstone/gemfire/test/dunit/standalone/ChildVM.java
>  PRE-CREATION 
>   
> gemfire-core/src/test/java/com/gemstone/gemfire/test/dunit/standalone/DUnitLauncher.java
>  PRE-CREATION 
>   
> gemfire-core/src/test/java/com/gemstone/gemfire/test/dunit/standalone/ProcessManager.java
>  PRE-CREATION 
>   
> gemfire-core/src/test/java/com/gemstone/gemfire/test/dunit/standalone/RemoteDUnitVM.java
>  PRE-CREATION 
>   
> gemfire-core/src/test/java/com/gemstone/gemfire/test/dunit/standalone/RemoteDUnitVMIF.java
>  PRE-CREATION 
>   
> gemfire-core/src/test/java/com/gemstone/gemfire/test/dunit/standalone/StandAloneDUnitEnv.java
>  PRE-CREATION 
>   
> gemfire-core/src/test/java/com/gemstone/gemfire/test/dunit/tests/BasicDUnitTest.java
>  PRE-CREATION 
>   
> gemfire-core/src/test/java/com/gemstone/gemfire/test/dunit/tests/VMDUnitTest.java
>  PRE-CREATION 
>   gemfire-core/src/test/java/dunit/BounceResult.java d8ac186 
>   gemfire-core/src/test/java/dunit/DUnitEnv.java 19c3635 
>   gemfire-core/src/test/java/dunit/DistributedTestCase.java 6fa560f 
>   gemfire-core/src/test/java/dunit/Host.java cc41316 
>   gemfire-core/src/test/java/dunit/RemoteDUnitVMIF.java 5dffa47 
>   gemfire-core/src/test/java/dunit/VM.java 3c0a7b7 
>   gemfire-core/src/test/java/dunit/standalone/ChildVM.java 45a236a 
>   gemfire-core/src/test/java/dunit/standalone/DUnitLauncher.java 6433389 
>   gemfire-core/src/test/java/dunit/standalone/ProcessManager.java 6366853 
>   gemfire-core/src/test/java/dunit/standalone/RemoteDUnitVM.java 742dc55 
>   gemfire-core/src/test/java/dunit/standalone/StandAloneDUnitEnv.java 085035d 
>   gemfire-core/src/test/java/dunit/tests/BasicDUnitTest.java c284b3a 
>   gemfire-core/src/test/java/dunit/tests/TestFailure.java 17a39fa 
>   gemfire-core/src/test/java/dunit/tests/VMDUnitTest.java 27736dc 
> 
> Diff: https://reviews.apache.org/r/42561/diff/
> 
> 
> Testing
> ---
> 
> precheckin (all tests)
> 
> 
> Thanks,
> 
> Kirk Lund
> 
>



Re: Can we tweak svngit2jira to ignore feature branches ?

2016-01-21 Thread Dan Smith
I haven't seen any disagreements with this proposal. Can we ask infra to
make the change?

-Dan

On Fri, Jan 8, 2016 at 5:40 PM, Anthony Baker  wrote:

> Yep.  I went though *lots* of tickets last night and ran into this all
> over.
>
> Anthony
>
> > On Jan 8, 2016, at 5:22 PM, Jacob Barrett  wrote:
> >
> > ++1
> >
> > On Fri, Jan 8, 2016 at 5:06 PM Dan Smith  wrote:
> >
> >> ++1
> >>
> >> We're currently getting lots of silly comments on tickets, Especially
> when
> >> downmerging from develop to a feature branch. See for example
> GEODE-364. It
> >> two messages with the same hash. The second one is reporting that the
> >> commit was merged to feature/GEODE-715. These extra messages just make
> the
> >> history of the ticket more confusing.
> >>
> >> -Dan
> >>
> >> On Fri, Jan 8, 2016 at 4:57 PM, William Markito 
> >> wrote:
> >>
> >>> The idea here is that feature branches would not update the JIRA
> tickets
> >>> anymore, just when they get merged to develop, release or master an
> entry
> >>> would be added to the JIRA comments.
> >>>
> >>> If we're ok with that I can go ahead and open that ticket with INFRA.
> >>>
> >>> Thanks!
> >>>
> >>> --
> >>>
> >>> William Markito Oliveira
> >>> -- For questions about Apache Geode, please write to
> >>> *dev@geode.incubator.apache.org
> >>> *
> >>>
> >>
>
>


Re: Review Request 42576: unit test DisconnectingOutOfOffHeapMemoryListener

2016-01-21 Thread Swapnil Bawaskar

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

Ship it!



gemfire-core/src/main/java/com/gemstone/gemfire/internal/offheap/DisconnectingOutOfOffHeapMemoryListener.java
 (line 21)


Could you please add a one liner javadoc here?


- Swapnil Bawaskar


On Jan. 21, 2016, 5:46 p.m., Darrel Schneider wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/42576/
> ---
> 
> (Updated Jan. 21, 2016, 5:46 p.m.)
> 
> 
> Review request for geode, Scott Jewell, Ken Howe, Sai Boorlagadda, and 
> Swapnil Bawaskar.
> 
> 
> Bugs: GEODE-814
> https://issues.apache.org/jira/browse/GEODE-814
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> Added unit test for DisconnectingOutOfOffHeapMemoryListener.
> 
> InternalDistributedSystem is no longer final so that unit tests can mock it. 
> The reason it was made final was because in an older version of the product 
> this class did license checking and we wanted to prevent it from being 
> subclassed.
> 
> 
> Diffs
> -
> 
>   
> gemfire-core/src/main/java/com/gemstone/gemfire/distributed/internal/InternalDistributedSystem.java
>  8f604b47a5e952ca62cbb2e7afece4750a7de0d3 
>   
> gemfire-core/src/main/java/com/gemstone/gemfire/internal/offheap/DisconnectingOutOfOffHeapMemoryListener.java
>  PRE-CREATION 
>   
> gemfire-core/src/main/java/com/gemstone/gemfire/internal/offheap/OffHeapStorage.java
>  c950134099ac58e6befeeb891a9cecc98a4d4f04 
>   
> gemfire-core/src/test/java/com/gemstone/gemfire/internal/offheap/DisconnectingOutOfOffHeapMemoryListenerTest.java
>  PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/42576/diff/
> 
> 
> Testing
> ---
> 
> DisconnectingOutOfOffHeapMemoryListenerJUnitTest
> 
> 
> Thanks,
> 
> Darrel Schneider
> 
>



Re: [ANNOUNCE] Donation of GemFire WAN and CQ code

2016-01-21 Thread Dan Smith
If no one objects, I'll start working on cleaning the wan_cq_donation
branch up as described in GEODE-801 tomorrow. This is just getting the code
ready to merge to develop, not the merge itself.

-Dan

On Wed, Jan 20, 2016 at 10:27 AM, Dan Smith  wrote:

> This is great!
>
> These two features are separate gradle modules, so there are no changes to
> existing code. As you are looking at the changes, all of the new code is in
> the gemfire-wan and gemfire-cq modules. One important point is that these
> modules are not adding new public API, they are providing implementations
> for these features using existing extensions points in geode - see
> WANServiceProvider and CQServiceProvider.
>
> There are a few things that need to happen with this code before it gets
> merged to develop, assuming we want to merge this in. I've created
> GEODE-801 to track that work. My suggestion is that we go ahead and get
> started on this work on the wan_cq_donation branch and then if we get
> consensus to merge the changes they will be ready to merge.
>
> If we merge these in to develop this does mean that our next geode release
> will contain these new modules. That might be as soon as 1.0.0.M2. But I
> think it would be better to go ahead and integrate this code sooner rather
> than later so these features are available to users. I'd be in favor of
> merging the changes after the subtasks of GEODE-801 are resolved and we've
> had a week or so to look at the changes and discuss the merge.
>
> -Dan
>
>
>
> On Tue, Jan 19, 2016 at 7:28 PM, Anthony Baker  wrote:
>
>> I am pleased to announce the donation of additional GemFire code to the
>> Geode community.  The code being donated adds significant capabilities used
>> by many GemFire customers in production, namely WAN replication and
>> Continuous Query.
>>
>> *WAN replication* provides event delivery and data synchronization for
>> multi-site distributed clusters.  Asynchronous, persistent event delivery
>> to remote systems enables patterns such Active/Active, Disaster Recovery,
>> or Follow-the-Sun with support for configurable, eventually consistent data
>> replication.  *Continuous Querying* allows clients to subscribe to server
>> events by using SQL-like query filtering.  Events that match or modify the
>> query results are queued and delivered to the client using the
>> client/server subscription framework.
>>
>> The Software Grant Agreement for this code has been accepted by the ASF
>> secretary.
>>
>> The donated code currently sits in a separate branch in the Geode
>> repository named wan_cq_donation [1] and is awaiting community feedback.  I
>> encourage everyone in the Geode community to review this donation and
>> provide feedback.  Once the community has reached a consensus we can
>> determine next steps and how this code might get merged into the develop
>> branch so that all users can access these features.  Your suggestions are
>> most welcome!
>>
>>
>> Thanks,
>> Anthony
>>
>> [1]
>> https://git1-us-west.apache.org/repos/asf?p=incubator-geode.git;a=tree;h=refs/heads/wan_cq_donation;hb=refs/heads/wan_cq_donation
>>
>>
>


Re: Review Request 42576: unit test DisconnectingOutOfOffHeapMemoryListener

2016-01-21 Thread Ken Howe

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

Ship it!


Regarding the comment on removing final from InternalDistributedSystem, if this 
class no longer has anything to do with licensing, then the comments on lines 
595 and 786 are misleading.

Test class naming standards are ...JUnitTest not ...Test. The Testing Done 
comment reflects the correct name, but the diffs show the name without "JUnit"

@Category annotation is missing from the test class.

- Ken Howe


On Jan. 21, 2016, 5:46 p.m., Darrel Schneider wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/42576/
> ---
> 
> (Updated Jan. 21, 2016, 5:46 p.m.)
> 
> 
> Review request for geode, Scott Jewell, Ken Howe, Sai Boorlagadda, and 
> Swapnil Bawaskar.
> 
> 
> Bugs: GEODE-814
> https://issues.apache.org/jira/browse/GEODE-814
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> Added unit test for DisconnectingOutOfOffHeapMemoryListener.
> 
> InternalDistributedSystem is no longer final so that unit tests can mock it. 
> The reason it was made final was because in an older version of the product 
> this class did license checking and we wanted to prevent it from being 
> subclassed.
> 
> 
> Diffs
> -
> 
>   
> gemfire-core/src/main/java/com/gemstone/gemfire/distributed/internal/InternalDistributedSystem.java
>  8f604b47a5e952ca62cbb2e7afece4750a7de0d3 
>   
> gemfire-core/src/main/java/com/gemstone/gemfire/internal/offheap/DisconnectingOutOfOffHeapMemoryListener.java
>  PRE-CREATION 
>   
> gemfire-core/src/main/java/com/gemstone/gemfire/internal/offheap/OffHeapStorage.java
>  c950134099ac58e6befeeb891a9cecc98a4d4f04 
>   
> gemfire-core/src/test/java/com/gemstone/gemfire/internal/offheap/DisconnectingOutOfOffHeapMemoryListenerTest.java
>  PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/42576/diff/
> 
> 
> Testing
> ---
> 
> DisconnectingOutOfOffHeapMemoryListenerJUnitTest
> 
> 
> Thanks,
> 
> Darrel Schneider
> 
>



[GitHub] incubator-geode pull request: Feature/geode 12

2016-01-21 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/incubator-geode/pull/70


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


Re: Pulse UI merged to develop

2016-01-21 Thread Gregory Chase
+ dev

On Thu, Jan 21, 2016 at 3:12 PM, Jens Deppe  wrote:

> Thanks to the work of Jinmei and Nitin, we now have the Geode Pulse UI
> merged to develop!
>
> This does not bring any new features with it, but does make the UI
> automatically available when starting a locator. More information about
> accessing Pulse can be found here:
> http://gemfire.docs.pivotal.io/docs-gemfire/latest/tools_modules/pulse/chapter_overview.html
>
> This does mean that Jiras can (and should) be filed against found bugs and
> for new features you would like to see in Pulse.
>
> After today's nightly build, you can download a distribution here to try
> it out: https://builds.apache.org/job/Geode-nightly/
>
> --Jens
>



-- 
Greg Chase

Director of Big Data Communities
http://www.pivotal.io/big-data

Pivotal Software
http://www.pivotal.io/

650-215-0477
@GregChase
Blog: http://geekmarketing.biz/


Re: Pulse UI merged to develop

2016-01-21 Thread Anthony Baker
Excellent!  Have the LICENSE / NOTICE files been updated based on the new 
source and binary dependencies?

Anthony

> On Jan 21, 2016, at 3:15 PM, Gregory Chase  wrote:
> 
> + dev
> 
> On Thu, Jan 21, 2016 at 3:12 PM, Jens Deppe  wrote:
> 
>> Thanks to the work of Jinmei and Nitin, we now have the Geode Pulse UI
>> merged to develop!
>> 
>> This does not bring any new features with it, but does make the UI
>> automatically available when starting a locator. More information about
>> accessing Pulse can be found here:
>> http://gemfire.docs.pivotal.io/docs-gemfire/latest/tools_modules/pulse/chapter_overview.html
>> 
>> This does mean that Jiras can (and should) be filed against found bugs and
>> for new features you would like to see in Pulse.
>> 
>> After today's nightly build, you can download a distribution here to try
>> it out: https://builds.apache.org/job/Geode-nightly/
>> 
>> --Jens
>> 
> 
> 
> 
> --
> Greg Chase
> 
> Director of Big Data Communities
> http://www.pivotal.io/big-data
> 
> Pivotal Software
> http://www.pivotal.io/
> 
> 650-215-0477
> @GregChase
> Blog: http://geekmarketing.biz/



signature.asc
Description: Message signed with OpenPGP using GPGMail


Re: Pulse UI merged to develop

2016-01-21 Thread Jinmei Liao
Oh, no, not yet. But all the sources brought over has the corresponding
license headers, and gradle rat is running successfully. Will update those
LICENSE/NOTICE soon.

On Thu, Jan 21, 2016 at 3:29 PM, Anthony Baker  wrote:

> Excellent!  Have the LICENSE / NOTICE files been updated based on the new
> source and binary dependencies?
>
> Anthony
>
> > On Jan 21, 2016, at 3:15 PM, Gregory Chase  wrote:
> >
> > + dev
> >
> > On Thu, Jan 21, 2016 at 3:12 PM, Jens Deppe 
> wrote:
> >
> >> Thanks to the work of Jinmei and Nitin, we now have the Geode Pulse UI
> >> merged to develop!
> >>
> >> This does not bring any new features with it, but does make the UI
> >> automatically available when starting a locator. More information about
> >> accessing Pulse can be found here:
> >>
> http://gemfire.docs.pivotal.io/docs-gemfire/latest/tools_modules/pulse/chapter_overview.html
> >>
> >> This does mean that Jiras can (and should) be filed against found bugs
> and
> >> for new features you would like to see in Pulse.
> >>
> >> After today's nightly build, you can download a distribution here to try
> >> it out: https://builds.apache.org/job/Geode-nightly/
> >>
> >> --Jens
> >>
> >
> >
> >
> > --
> > Greg Chase
> >
> > Director of Big Data Communities
> > http://www.pivotal.io/big-data
> >
> > Pivotal Software
> > http://www.pivotal.io/
> >
> > 650-215-0477
> > @GregChase
> > Blog: http://geekmarketing.biz/
>
>


-- 
Cheers

Jinmei


Re: [VOTE] Apache Geode (Incubating) first Milestone release - v1.0.0-incubating.M1

2016-01-21 Thread Kenneth Howe
I’m installing the M1 release from the source distribution (.tar.gz) and have 
noted a couple
issues:

1. The gradle wrapper script, gradlew, is missing. I expected to find this 
script at the top level of the un-zipped archive, where it is when cloning the 
incubator-geode git repo. Building with this script rather than directly 
executing grade is the recommended procedure as shown in COMPILING.txt and in 
the “Geode in 5 minutes” section of README.md.

2. It was my understanding that Geode is targeted to idk 1.8. The “Geode in 5 
minutes” in README.md specifies jdk1.7.75.

Ken Howe

> On Jan 19, 2016, at 1:53 PM, Nitin Lamba  wrote:
> 
> This is the first release for Apache Geode, version 1.0.0-incubating.M1. 
> Thanks to all the community members to drive towards this first milestone!
> 
> It fixes the following issues:
>   
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318420&version=12334248
> 
> *** Please download, test and vote by Wednesday, January 20th, 1700 hrs US 
> Pacific.
> 
> Note that we are voting upon the source (tag):
>   rel/1.0.0-incubating.M1.RC1
> 
>   
> https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;a=tag;h=refs/tags/rel/v1.0.0-incubating.M1.RC1
> 
> 
> Commit ID: e5a7b9aaa82d4c0a04e41febfd515056c4669001
> 
>   
> https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;a=commit;h=e5a7b9aaa82d4c0a04e41febfd515056c4669001
> 
> 
> Source and binary files:
>   
> https://dist.apache.org/repos/dist/dev/incubator/geode/1.0.0-incubating.M1.RC1/
> 
> For the first release, the documentation on how to install and use Apache 
> Geode are hosted on pivotal.io:
>   http://geode.docs.pivotal.io
> 
> 
> Maven staging repo:
>   https://repository.apache.org/content/repositories/orgapachegeode-1000/
> 
> 
> Geode's KEYS file containing PGP keys we use to sign the release:
>   
> https://github.com/apache/incubator-geode/blob/release/1.0.0-incubating.M1/KEYS
> 
> 
> Release Key: pub  4096R/C72CFB64 2015-10-01
> 
> Thanks,
> Nitin & Anthony
> 
> 
> 
> 



Review Request 42624: split the unit test up into two and removed duplicate test code

2016-01-21 Thread Darrel Schneider

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

Review request for geode and Dan Smith.


Bugs: GEODE-827
https://issues.apache.org/jira/browse/GEODE-827


Repository: geode


Description
---

Split the unit test up into two and removed duplicate test code.
Also changed the new integration tests methods to run for 5 seconds instead of 
60.


Diffs
-

  
gemfire-core/src/test/java/com/gemstone/gemfire/internal/offheap/SimpleMemoryAllocatorFillPatternIntegrationTest.java
 PRE-CREATION 
  
gemfire-core/src/test/java/com/gemstone/gemfire/internal/offheap/SimpleMemoryAllocatorFillPatternJUnitTest.java
 12f5d22f76e88265f07b4e708ff8ec611e5540b6 

Diff: https://reviews.apache.org/r/42624/diff/


Testing
---

ran both unit test cases


Thanks,

Darrel Schneider



Re: Review Request 42624: split the unit test up into two and removed duplicate test code

2016-01-21 Thread Dan Smith

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

Ship it!


Ship It!

- Dan Smith


On Jan. 22, 2016, 12:22 a.m., Darrel Schneider wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/42624/
> ---
> 
> (Updated Jan. 22, 2016, 12:22 a.m.)
> 
> 
> Review request for geode and Dan Smith.
> 
> 
> Bugs: GEODE-827
> https://issues.apache.org/jira/browse/GEODE-827
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> Split the unit test up into two and removed duplicate test code.
> Also changed the new integration tests methods to run for 5 seconds instead 
> of 60.
> 
> 
> Diffs
> -
> 
>   
> gemfire-core/src/test/java/com/gemstone/gemfire/internal/offheap/SimpleMemoryAllocatorFillPatternIntegrationTest.java
>  PRE-CREATION 
>   
> gemfire-core/src/test/java/com/gemstone/gemfire/internal/offheap/SimpleMemoryAllocatorFillPatternJUnitTest.java
>  12f5d22f76e88265f07b4e708ff8ec611e5540b6 
> 
> Diff: https://reviews.apache.org/r/42624/diff/
> 
> 
> Testing
> ---
> 
> ran both unit test cases
> 
> 
> Thanks,
> 
> Darrel Schneider
> 
>



Re: Pulse UI merged to develop

2016-01-21 Thread Nitin Lamba
Great progress - thanks Jinmei and Jens!

Tried to build 'develop' on my machine and started Pulse - launched as 
expected. How does one launch UITests? I see those tests removed form 
build.gradle file that were worked on last year.

As mentioned, Pivotal/ Gemfire branding on the UI is still not fixed - see 
attached. Per the JIRA[1], licensing was worked on a bit last November but 
haven't seen any recent updates. The top-level JIRA (GEODE-12) captures all the 
pending items - still a few unresolved.

Ideally, shouldn't all the issues be addressed before merging into develop?

- Nitin
[1] https://issues.apache.org/jira/browse/GEODE-511


From: Jinmei Liao 
Sent: Thursday, January 21, 2016 3:32 PM
To: dev@geode.incubator.apache.org
Subject: Re: Pulse UI merged to develop

Oh, no, not yet. But all the sources brought over has the corresponding
license headers, and gradle rat is running successfully. Will update those
LICENSE/NOTICE soon.

On Thu, Jan 21, 2016 at 3:29 PM, Anthony Baker  wrote:

> Excellent!  Have the LICENSE / NOTICE files been updated based on the new
> source and binary dependencies?
>
> Anthony
>
> > On Jan 21, 2016, at 3:15 PM, Gregory Chase  wrote:
> >
> > + dev
> >
> > On Thu, Jan 21, 2016 at 3:12 PM, Jens Deppe 
> wrote:
> >
> >> Thanks to the work of Jinmei and Nitin, we now have the Geode Pulse UI
> >> merged to develop!
> >>
> >> This does not bring any new features with it, but does make the UI
> >> automatically available when starting a locator. More information about
> >> accessing Pulse can be found here:
> >>
> http://gemfire.docs.pivotal.io/docs-gemfire/latest/tools_modules/pulse/chapter_overview.html
> >>
> >> This does mean that Jiras can (and should) be filed against found bugs
> and
> >> for new features you would like to see in Pulse.
> >>
> >> After today's nightly build, you can download a distribution here to try
> >> it out: https://builds.apache.org/job/Geode-nightly/
> >>
> >> --Jens
> >>
> >
> >
> >
> > --
> > Greg Chase
> >
> > Director of Big Data Communities
> > http://www.pivotal.io/big-data
> >
> > Pivotal Software
> > http://www.pivotal.io/
> >
> > 650-215-0477
> > @GregChase
> > Blog: http://geekmarketing.biz/
>
>


--
Cheers

Jinmei

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #197 was SUCCESSFUL (with 1222 tests)

2016-01-21 Thread Spring CI

---
Spring Data GemFire > Nightly-ApacheGeode > #197 was successful.
---
Scheduled
1226 tests in total.

https://build.spring.io/browse/SGF-NAG-197/





--
This message is automatically generated by Atlassian Bamboo

Re: Pulse UI merged to develop

2016-01-21 Thread Jinmei Liao
To run all the UI tests, you just do "./gradlew uiTest" in the command
line. Currently these tests are not run in Jenkins since it would require
Firefox to be launched. All the PulseAutomatedTest, PulseBaseTest and
PulseTest are run as uiTest.

licenses are updated on each file. Will update the LICENSE and NOTICE as
well.

As to the branding, I believe we will still leave Jira around to capture
the work to be done.

On Thu, Jan 21, 2016 at 5:43 PM, Nitin Lamba  wrote:

> Great progress - thanks Jinmei and Jens!
>
> Tried to build 'develop' on my machine and started Pulse - launched as
> expected. How does one launch UITests? I see those tests removed form
> build.gradle file that were worked on last year.
>
> As mentioned, Pivotal/ Gemfire branding on the UI is still not fixed - see
> attached. Per the JIRA[1], licensing was worked on a bit last November but
> haven't seen any recent updates. The top-level JIRA (GEODE-12) captures all
> the pending items - still a few unresolved.
>
> Ideally, shouldn't all the issues be addressed before merging into develop?
>
> - Nitin
> [1] https://issues.apache.org/jira/browse/GEODE-511
>
> 
> From: Jinmei Liao 
> Sent: Thursday, January 21, 2016 3:32 PM
> To: dev@geode.incubator.apache.org
> Subject: Re: Pulse UI merged to develop
>
> Oh, no, not yet. But all the sources brought over has the corresponding
> license headers, and gradle rat is running successfully. Will update those
> LICENSE/NOTICE soon.
>
> On Thu, Jan 21, 2016 at 3:29 PM, Anthony Baker  wrote:
>
> > Excellent!  Have the LICENSE / NOTICE files been updated based on the new
> > source and binary dependencies?
> >
> > Anthony
> >
> > > On Jan 21, 2016, at 3:15 PM, Gregory Chase  wrote:
> > >
> > > + dev
> > >
> > > On Thu, Jan 21, 2016 at 3:12 PM, Jens Deppe 
> > wrote:
> > >
> > >> Thanks to the work of Jinmei and Nitin, we now have the Geode Pulse UI
> > >> merged to develop!
> > >>
> > >> This does not bring any new features with it, but does make the UI
> > >> automatically available when starting a locator. More information
> about
> > >> accessing Pulse can be found here:
> > >>
> >
> http://gemfire.docs.pivotal.io/docs-gemfire/latest/tools_modules/pulse/chapter_overview.html
> > >>
> > >> This does mean that Jiras can (and should) be filed against found bugs
> > and
> > >> for new features you would like to see in Pulse.
> > >>
> > >> After today's nightly build, you can download a distribution here to
> try
> > >> it out: https://builds.apache.org/job/Geode-nightly/
> > >>
> > >> --Jens
> > >>
> > >
> > >
> > >
> > > --
> > > Greg Chase
> > >
> > > Director of Big Data Communities
> > > http://www.pivotal.io/big-data
> > >
> > > Pivotal Software
> > > http://www.pivotal.io/
> > >
> > > 650-215-0477
> > > @GregChase
> > > Blog: http://geekmarketing.biz/
> >
> >
>
>
> --
> Cheers
>
> Jinmei
>



-- 
Cheers

Jinmei