---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/55603/#review161817
---
Ship it!
geode-wan/src/test/java/org/apache/geode/management/i
An upcoming change we need to decide on is the C++ and .NET namespace for
the C++ and .NET clients.
*C++*
Current:
*::gemfire*
Thoughts:
*::apache::geode::client*
*::geode::client*
I shy away from prefixing with *apache* since it requires extra blocks in
C++:
(formatted to Google C++ style guide)
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/55532/
---
(Updated Jan. 17, 2017, 5:07 a.m.)
Review request for geode, Jared Stewart, Kev
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/55603/
---
(Updated Jan. 17, 2017, 5:03 a.m.)
Review request for geode, Jared Stewart, Kev
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/55603/
---
Review request for geode, Jared Stewart, Kevin Duling, and Kirk Lund.
Repositor
Roman or Mark,
Reading the list of build tools on the Jenkins slaves it sounds like these
boxes are geared solely towards Java compilation. Is there a build system
or slave for building native bits?
We will need GCC 4.9 or newer (C++11), CMake, Doxygen, and a few other
tools.
Thanks,
Jake
On M
Roman,
I understand what you are saying. I think that since the build process
between the Java Geode bits and the Native Geode bits will completely
different it might help to have the separate. Until someone comes up with a
good cross platform and cross language build tool that is commonly used in
[
https://issues.apache.org/jira/browse/GEODE-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824970#comment-15824970
]
ASF subversion and git services commented on GEODE-1733:
Commit 45
[
https://issues.apache.org/jira/browse/GEODE-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824781#comment-15824781
]
ASF GitHub Bot commented on GEODE-2031:
---
Github user joeymcallister closed the pull
Github user joeymcallister closed the pull request at:
https://github.com/apache/geode/pull/334
---
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
[
https://issues.apache.org/jira/browse/GEODE-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824767#comment-15824767
]
ASF GitHub Bot commented on GEODE-2031:
---
GitHub user joeymcallister reopened a pull
GitHub user joeymcallister reopened a pull request:
https://github.com/apache/geode/pull/334
Feature/geode 2031
This PR accomplishes a few things:
1. As outlined in the GEODE-2031 ticket, I've adjusted the flow so we can
now publish older versions of the docs in addition to the
[
https://issues.apache.org/jira/browse/GEODE-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824761#comment-15824761
]
ASF GitHub Bot commented on GEODE-2031:
---
Github user joeymcallister closed the pull
Github user joeymcallister closed the pull request at:
https://github.com/apache/geode/pull/334
---
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
Here's my own, personal minority report: I think that a separate repo
will complicate your build and release process and will fracture your
nascent community. That said...
On Mon, Jan 16, 2017 at 3:58 PM, Jacob Barrett wrote:
> Mark,
>
> Looks like we have lots of votes for your separate repo ide
Github user asfgit closed the pull request at:
https://github.com/apache/geode/pull/340
---
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 enabl
Mark,
Looks like we have lots of votes for your separate repo idea. What do we
need to do to get that going?
On that note too, do you know who we need to ping to get a build going? I
would suggest we target Linux first since it is the easiest. The tools
necessary can be found in the src/BUILDING.
[
https://issues.apache.org/jira/browse/GEODE-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob S. Barrett resolved GEODE-2307.
-
Resolution: Fixed
> Add FindGeode CMake module to native client build for finding Geode
>
[
https://issues.apache.org/jira/browse/GEODE-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824727#comment-15824727
]
ASF subversion and git services commented on GEODE-2031:
Commit 3b
[
https://issues.apache.org/jira/browse/GEODE-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824732#comment-15824732
]
ASF subversion and git services commented on GEODE-2031:
Commit 51
[
https://issues.apache.org/jira/browse/GEODE-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824729#comment-15824729
]
ASF subversion and git services commented on GEODE-2031:
Commit b8
[
https://issues.apache.org/jira/browse/GEODE-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824730#comment-15824730
]
ASF subversion and git services commented on GEODE-2031:
Commit 50
[
https://issues.apache.org/jira/browse/GEODE-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824731#comment-15824731
]
ASF subversion and git services commented on GEODE-2031:
Commit 3b
[
https://issues.apache.org/jira/browse/GEODE-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824728#comment-15824728
]
ASF subversion and git services commented on GEODE-2031:
Commit 42
[
https://issues.apache.org/jira/browse/GEODE-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824726#comment-15824726
]
ASF subversion and git services commented on GEODE-2031:
Commit b1
[
https://issues.apache.org/jira/browse/GEODE-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824724#comment-15824724
]
ASF subversion and git services commented on GEODE-2031:
Commit ec
Avinash,
We just added some changes to the Geode dependency. You should be able to
set cmake -DGEODE_ROOT=/path/to/apache-geode. Without that flag set it will
look for Geode in:
/geode/bin
/apache-geode/bin
/usr/geode/bin
/usr/apache-geode/bin
/usr/local/geode/bin
/usr/local/apache-ge
[
https://issues.apache.org/jira/browse/GEODE-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824725#comment-15824725
]
ASF subversion and git services commented on GEODE-2031:
Commit a0
GitHub user jaredjstewart opened a pull request:
https://github.com/apache/geode/pull/340
Restore constructor used for Mocks
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jaredjstewart/geode GEODE-2272
Alternatively you can re
[
https://issues.apache.org/jira/browse/GEODE-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824712#comment-15824712
]
ASF subversion and git services commented on GEODE-2307:
Commit 53
[
https://issues.apache.org/jira/browse/GEODE-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob S. Barrett resolved GEODE-2310.
-
Resolution: Fixed
> Native client is looking for specific version of Geode jar.
>
[
https://issues.apache.org/jira/browse/GEODE-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824700#comment-15824700
]
ASF subversion and git services commented on GEODE-2296:
Commit f4
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/55442/#review161800
---
Ship it!
Ship It!
- xiaojian zhou
On Jan. 16, 2017, 7:37 p.m
[
https://issues.apache.org/jira/browse/GEODE-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Martell updated GEODE-2311:
---
Priority: Minor (was: Major)
> Add CSharp Project for securityImpl for Building Native Client
[
https://issues.apache.org/jira/browse/GEODE-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Martell updated GEODE-2311:
---
Description: Since cmake doesn't yet support C#, we should provide a CSharp
project (.csproj f
Michael Martell created GEODE-2311:
--
Summary: Add CSharp Project for securityImpl for Building Native
Client .NET Security Quickstarts
Key: GEODE-2311
URL: https://issues.apache.org/jira/browse/GEODE-2311
[
https://issues.apache.org/jira/browse/GEODE-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824686#comment-15824686
]
ASF GitHub Bot commented on GEODE-2272:
---
Github user asfgit closed the pull request
[
https://issues.apache.org/jira/browse/GEODE-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824684#comment-15824684
]
ASF subversion and git services commented on GEODE-2310:
Commit ef
[
https://issues.apache.org/jira/browse/GEODE-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824685#comment-15824685
]
ASF subversion and git services commented on GEODE-2272:
Commit f8
Github user asfgit closed the pull request at:
https://github.com/apache/geode/pull/339
---
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 enabl
---
Spring Data GemFire > Nightly-ApacheGeode > #440 was successful.
---
Scheduled
https://build.spring.io/browse/SGF-NAG-440/
--
This message is automatica
[
https://issues.apache.org/jira/browse/GEODE-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824681#comment-15824681
]
ASF GitHub Bot commented on GEODE-2272:
---
GitHub user jaredjstewart opened a pull req
[
https://issues.apache.org/jira/browse/GEODE-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824682#comment-15824682
]
ASF GitHub Bot commented on GEODE-2272:
---
Github user jaredjstewart commented on the
GitHub user jaredjstewart opened a pull request:
https://github.com/apache/geode/pull/339
GEODE-2272: Fix Pulse data browser export
* Pulse no longer loads all results into the browser before generating a
results file for download.
You can merge this pull request into a Git reposit
Github user jaredjstewart commented on the issue:
https://github.com/apache/geode/pull/339
Precheckin started
---
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 s
Jacob S. Barrett created GEODE-2310:
---
Summary: Native client is looking for specific version of Geode
jar.
Key: GEODE-2310
URL: https://issues.apache.org/jira/browse/GEODE-2310
Project: Geode
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/55591/#review161794
---
Ship it!
Ship It!
- Jared Stewart
On Jan. 16, 2017, 10 p.m.,
[
https://issues.apache.org/jira/browse/GEODE-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-2308:
-
Fix Version/s: (was: 1.1.0)
> Replace GemFire branding with Geode branding.
>
[
https://issues.apache.org/jira/browse/GEODE-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-2307:
-
Fix Version/s: (was: 1.1.0)
> Add FindGeode CMake module to native client build for finding Ge
[
https://issues.apache.org/jira/browse/GEODE-2309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-2309:
-
Fix Version/s: (was: 1.1.0)
> Replace or add ASF copyright statements in source.
> ---
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/55591/#review161791
---
geode-core/src/main/java/org/apache/geode/internal/logging/log4j/
[
https://issues.apache.org/jira/browse/GEODE-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-2306:
-
Fix Version/s: (was: 1.1.0)
> Update native client BUILDING.md to reflect changes for Geode
>
[
https://issues.apache.org/jira/browse/GEODE-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dodge reassigned GEODE-2306:
Assignee: Michael Dodge
> Update native client BUILDING.md to reflect changes for Geode
> -
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/55591/
---
Review request for geode, Bruce Schuchardt, Darrel Schneider, Jinmei Liao,
Jared
[
https://issues.apache.org/jira/browse/GEODE-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824626#comment-15824626
]
ASF subversion and git services commented on GEODE-2297:
Commit de
[
https://issues.apache.org/jira/browse/GEODE-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824611#comment-15824611
]
ASF GitHub Bot commented on GEODE-2272:
---
Github user jaredjstewart commented on the
[
https://issues.apache.org/jira/browse/GEODE-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824612#comment-15824612
]
ASF GitHub Bot commented on GEODE-2272:
---
Github user jaredjstewart closed the pull r
Github user jaredjstewart commented on the issue:
https://github.com/apache/geode/pull/338
Closing for now due precheckin failures
---
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
Github user jaredjstewart closed the pull request at:
https://github.com/apache/geode/pull/338
---
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 i
+1 for a separate repo per client.
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: 631-835-4771
On Mon, Jan 16, 2017 at 4:02 PM, Swapnil Bawaskar
wrote:
> +1 for a separate repo for each client.
>
> On Mon, Jan 16, 2017 at 12:25 PM, Joey McAllister
> wrote:
>
> > +1 to the se
[
https://issues.apache.org/jira/browse/GEODE-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob S. Barrett resolved GEODE-2305.
-
Resolution: Fixed
Assignee: Jacob S. Barrett
Fix Version/s: (was: 1.1.0
+1 for a separate repo for each client.
On Mon, Jan 16, 2017 at 12:25 PM, Joey McAllister
wrote:
> +1 to the separate repo.
>
> I think it also makes sense—especially with independent release
> schedules—to keep the client documentation source in the client repo and
> build it as its own User Gu
[
https://issues.apache.org/jira/browse/GEODE-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824583#comment-15824583
]
ASF subversion and git services commented on GEODE-2305:
Commit 7a
[
https://issues.apache.org/jira/browse/GEODE-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nabarun reassigned GEODE-2273:
--
Assignee: nabarun
> Display the server name while listing the Lucene index stats
>
[
https://issues.apache.org/jira/browse/GEODE-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nabarun updated GEODE-1733:
---
Fix Version/s: 1.1.0
> Lucene indexes stats are zeroed after recovering from indexes from disk
> -
[
https://issues.apache.org/jira/browse/GEODE-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nabarun resolved GEODE-1733.
Resolution: Fixed
> Lucene indexes stats are zeroed after recovering from indexes from disk
> --
[
https://issues.apache.org/jira/browse/GEODE-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nabarun updated GEODE-2273:
---
Component/s: lucene
> Display the server name while listing the Lucene index stats
> -
I suppose that one is sufficient to cover both but it would be nice to
narrow down on specific clients.
It is coming from it's own JIRA where we had components for:
C++ library
.NET library
test (for test framework issues)
install (for installer issues)
docs
build
Would be nice to be able to cove
Jacob S. Barrett created GEODE-2309:
---
Summary: Replace or add ASF copyright statements in source.
Key: GEODE-2309
URL: https://issues.apache.org/jira/browse/GEODE-2309
Project: Geode
Issue
Jacob S. Barrett created GEODE-2308:
---
Summary: Replace GemFire branding with Geode branding.
Key: GEODE-2308
URL: https://issues.apache.org/jira/browse/GEODE-2308
Project: Geode
Issue Type:
Update: We are waiting on following tickets for first release candidate.
1. GEODE-2296 GetFunctionAttribute command is throwing an Anonymouse User
Exception
2. GEODE-2277 client cache fails to deserialize a PdxInstance due to
InternalGemFireError
3. GEODE-2031 Host documentation for releases
[
https://issues.apache.org/jira/browse/GEODE-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob S. Barrett updated GEODE-2307:
Description: Native client build has dependencies on the Geode product
installation. FindGeo
Jacob S. Barrett created GEODE-2307:
---
Summary: Add FindGeode CMake module to native client build for
finding Geode installation
Key: GEODE-2307
URL: https://issues.apache.org/jira/browse/GEODE-2307
Jacob S. Barrett created GEODE-2305:
---
Summary: Remove native client packaging dependency on Pivotal EULA
Key: GEODE-2305
URL: https://issues.apache.org/jira/browse/GEODE-2305
Project: Geode
Jacob S. Barrett created GEODE-2306:
---
Summary: Update native client BUILDING.md to reflect changes for
Geode
Key: GEODE-2306
URL: https://issues.apache.org/jira/browse/GEODE-2306
Project: Geode
We do have an existing "native client" component. What should we do with that?
Thanks,
Roman.
On Mon, Jan 16, 2017 at 12:00 PM, Jacob Barrett wrote:
> Would someone with some karma please add some components to the JIRA for
> native client.
>
> At a minimum "C++ client" and ".NET client" compone
+1 to the separate repo.
I think it also makes sense—especially with independent release
schedules—to keep the client documentation source in the client repo and
build it as its own User Guide, which we can host in its own section on
geode.apache.org/docs/.
On Mon, Jan 16, 2017 at 12:14 PM Udo Ko
Thanks, Karen. Let me know if you have any questions.
On Mon, Jan 16, 2017 at 11:56 AM Karen Miller wrote:
> I'm going to pull this in and then update Geode web page.
>
>
> On Wed, Jan 11, 2017 at 4:50 PM, joeymcallister
> wrote:
>
> > Github user joeymcallister commented on a diff in the pull
+1 to separate client repos. Or at least some ability to independently
version client code for releases.
--Udo
On 1/16/17 11:56, Jacob Barrett wrote:
+1 for separate repo for sub-projects that would or could likely release
independently of the core project. I see this applying to most clients
+1 Separate repo for clients...Jake has valid point...
-Anil.
On Mon, Jan 16, 2017 at 12:07 PM, Michael William Dodge
wrote:
> +1 for at least a separate repo for the clients. Jake makes a good point
> about dependencies on different toolchains. I'm not sure whether that would
> merit have a s
+1 for at least a separate repo for the clients. Jake makes a good point about
dependencies on different toolchains. I'm not sure whether that would merit
have a separate repo for each platform's client, e.g., a repo for the Java
client, a repo for the C# client, etc. My instinct is to divide th
Would someone with some karma please add some components to the JIRA for
native client.
At a minimum "C++ client" and ".NET client" components would be helpful.
Thanks,
Jake
[
https://issues.apache.org/jira/browse/GEODE-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824518#comment-15824518
]
ASF GitHub Bot commented on GEODE-2295:
---
Github user galen-pivotal commented on the
> On Jan 16, 2017, at 11:49 AM, Jacob Barrett wrote:
>
> So you envision a world where someone who doesn't care about native clients
> must build the native clients as part of the root gradle build and a person
> not interested in building the Java bits must you gradle to build the
> native clie
[
https://issues.apache.org/jira/browse/GEODE-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824519#comment-15824519
]
ASF GitHub Bot commented on GEODE-2295:
---
Github user galen-pivotal closed the pull r
Github user galen-pivotal commented on the issue:
https://github.com/apache/geode/pull/337
Moving to review board.
---
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 wis
Github user galen-pivotal closed the pull request at:
https://github.com/apache/geode/pull/337
---
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 i
+1 for separate repo for sub-projects that would or could likely release
independently of the core project. I see this applying to most clients,
.net, c++, python, etc. It also cleanly separates out the build process
which is quite different between these projects. The native clients in
particular
I'm going to pull this in and then update Geode web page.
On Wed, Jan 11, 2017 at 4:50 PM, joeymcallister wrote:
> Github user joeymcallister commented on a diff in the pull request:
>
> https://github.com/apache/geode/pull/334#discussion_r95706396
>
> --- Diff: geode-book/README.md ---
I’m cautiously in favor of this idea. Allowing independent parts (geode,
geode-examples, geode-native) to progress and release at their own pace seems
like a good thing.
From a release perspective, I think each repo would have separate vote threads
and a section on our release page: http://ge
So you envision a world where someone who doesn't care about native clients
must build the native clients as part of the root gradle build and a person
not interested in building the Java bits must you gradle to build the
native clients?
Both those scenarios don't sound great to me. As a developer
> On Jan. 12, 2017, 5:26 p.m., Dan Smith wrote:
> > I'd say actually get rid of the distributed member id part and just keep
> > the name.
> >
> > Also, I don't think it's good practice to look up a singleton inside the
> > constructor for LuceneIndexDetails. It would be better just pass the s
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/55442/
---
(Updated Jan. 16, 2017, 7:37 p.m.)
Review request for geode, Barry Oglesby, Jas
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/55393/#review161776
---
Ship it!
Ship It!
- Mark Bretl
On Jan. 10, 2017, 2:39 p.m.,
[
https://issues.apache.org/jira/browse/GEODE-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824477#comment-15824477
]
Anthony Baker commented on GEODE-2264:
--
Based on the discussion from dev@geode this i
[
https://issues.apache.org/jira/browse/GEODE-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker resolved GEODE-2264.
--
Resolution: Not A Problem
> Update Geode Javadocs (no longer "incubating")
> ---
It's been a full week, but I haven't gotten any reviews on GEODE-2260, to
remove the geode-examples module from the geode repository. I'm not
a build/gradle expert, and this commit changes the build, so it really needs
some reviews.
The review request is https://reviews.apache.org/r/55393/
Thank
[
https://issues.apache.org/jira/browse/GEODE-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Udo Kohlmeyer updated GEODE-697:
Assignee: Darrel Schneider (was: Bruce Schuchardt)
> A client thread timing out an operation and per
[
https://issues.apache.org/jira/browse/GEODE-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Udo Kohlmeyer updated GEODE-697:
Component/s: (was: client/server)
regions
> A client thread timing out an operat
[
https://issues.apache.org/jira/browse/GEODE-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824466#comment-15824466
]
Udo Kohlmeyer commented on GEODE-697:
-
I agree with [~hitesh.khamesra] that the most im
1 - 100 of 140 matches
Mail list logo