[GitHub] geode pull request #343: GEODE-1435 Update LICENCE and NOTICE

GitHub user metatype opened a pull request: https://github.com/apache/geode/pull/343 GEODE-1435 Update LICENCE and NOTICE This should cover the bundled source components. You can merge this pull request into a Git repository by running: $ git pull

Re: Native Namespace

+1 for Apache.Geode.Client ( .net ) and apache::geode::client( C++ ) Thanks Avinash On Wed, Jan 18, 2017 at 3:17 AM, Jacob Barrett wrote: > Anthony, > > You make a good argument. Have fun converting all those namespaces for us > in your free time. :) > >

[jira] [Updated] (GEODE-1435) Update LICENSE for native client bundled dependencies

[ https://issues.apache.org/jira/browse/GEODE-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-1435: - Description: We need to declare attribution for any bundled dependencies in the native client

Re: Addressing OOM while recovering overflow regions.

Anil, option 1 looks good. Just have a small question. Will the option 1 implementation going to replace the existing implementation where we recover everything? Or will this be a default and still user will be able to use old/existing way based on some configuration where recovering everything.

Re: Addressing OOM while recovering overflow regions.

Can I assume all options load keys? If so, yes skip loading values. -- Mike Stolz Principal Engineer - Gemfire Product Manager Mobile: 631-835-4771 On Jan 17, 2017 5:48 PM, "Anilkumar Gingade" wrote: > Hi Geode Devs, > > We are working on ticket GEODE-1672, related to out

Re: Review Request 55440: GEODE-1733: Index repository is now created when the chunk bucket becomes primary.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55440/ --- (Updated Jan. 18, 2017, 4:19 a.m.) Review request for geode, Barry Oglesby,

[jira] [Updated] (GEODE-2316) Replace GemFire namespace with Geode namespace

[ https://issues.apache.org/jira/browse/GEODE-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob S. Barrett updated GEODE-2316: Fix Version/s: (was: 1.1.0) > Replace GemFire namespace with Geode namespace >

[jira] [Created] (GEODE-2318) Improve geode-examples build

Anthony Baker created GEODE-2318: Summary: Improve geode-examples build Key: GEODE-2318 URL: https://issues.apache.org/jira/browse/GEODE-2318 Project: Geode Issue Type: Bug

[GitHub] geode-examples issue #2: Build updates for examples

Github user metatype commented on the issue: https://github.com/apache/geode-examples/pull/2 We have an ASF-developed `gradlew` script that does not require the `gradle-wrapper.jar` file to be present, unlike the version from the gradle distribution. We don't have an equivalent

Re: Native client build fails linking shared library?

You might need the dev package of libz, something like libz-dev to be installed. On Wed, Jan 18, 2017 at 6:48 AM, Hitesh Khamesra < hitesh...@yahoo.com.invalid> wrote: > see if this link helps "http://stackoverflow.com/ > questions/32036372/ubuntu-14-04-rails-missing-file" > > > From: Dan

[GitHub] geode-examples issue #2: Build updates for examples

Github user jdeppe-pivotal commented on the issue: https://github.com/apache/geode-examples/pull/2 I'm not sure I understand the issue with `gradlew.bat`. Why raise the bar for Windows devs? --- If your project is set up for it, you can reply to this email and have your reply appear

Re: Native client build fails linking shared library?

see if this link helps "http://stackoverflow.com/questions/32036372/ubuntu-14-04-rails-missing-file; From: Dan Smith To: dev@geode.apache.org Sent: Tuesday, January 17, 2017 5:04 PM Subject: Re: Native client build fails linking shared library? Here's the

Re: Addressing OOM while recovering overflow regions.

I think that #1 is a good start... I think we should have all regions created before we recover from the files, or at least for the regions that use the diskstore being recovered. When we recover, do we start recovering in reverse? I mean, the latest data *should* be in the last data files,

Re: Native client build fails linking shared library?

All I can guess is that /usr/lib/libz.* is missing for some reason. Unless Jake has a better suggestion, I'll have to take a look at it tomorrow, in person if possible. Sarge > On 17 Jan, 2017, at 17:04, Dan Smith wrote: > > Here's the results of the VERBOSE make. I do see

Re: Native client build fails linking shared library?

Here's the results of the VERBOSE make. I do see a -lz in the linker line. [ 28%] Linking CXX executable gfcppcache_unittests cd /home/dan/MyStuff/Code/gemfire/native/cppcache/test && /usr/bin/cmake -E cmake_link_script CMakeFiles/gfcppcache_unittests.dir/link.txt --verbose=1 /usr/bin/c++ -g

Re: [ANNOUNCE] Donation of improved GemFire native client

I agree with Jake - I don't think having a single build process really serves either side well. In all my time using GemFire/Geode I've never once had a need to build (or even use) the Native Client component. Given that the majority of users/developers will be only Java focused, I don't think

[jira] [Commented] (GEODE-2306) 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:comment-tabpanel=15827164#comment-15827164 ] ASF subversion and git services commented on GEODE-2306: Commit

[jira] [Commented] (GEODE-2306) 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:comment-tabpanel=15827165#comment-15827165 ] ASF subversion and git services commented on GEODE-2306: Commit

[jira] [Commented] (GEODE-2306) 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:comment-tabpanel=15827162#comment-15827162 ] ASF subversion and git services commented on GEODE-2306: Commit

[jira] [Commented] (GEODE-2306) 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:comment-tabpanel=15827161#comment-15827161 ] ASF subversion and git services commented on GEODE-2306: Commit

Re: Native client build fails linking shared library?

Dan, Add VERBOSE=1 to your make command. make -j8 VERBOSE=1 To see details of the compile commands. Some of the third party dependencies won't show them but give it a try. -Jake On Tue, Jan 17, 2017 at 4:34 PM Michael William Dodge wrote: > Do you see -lz in the link

Re: Addressing OOM while recovering overflow regions.

I like number 1 On Tue, Jan 17, 2017 at 3:56 PM Dan Smith wrote: > Option 1 is not a bad idea. Another thought might be to not start > asynchronous value recovery until all of the regions are created. I think > right now we launch a task to read all of the oplogs and recover

Re: Native client build fails linking shared library?

Do you see -lz in the link line? Sarge > On 17 Jan, 2017, at 16:24, Dan Smith wrote: > > I tried building the next-gen-native-client-software-grant branch on an > ubuntu 16.04 box. It gets about halfway through and then fails with these > errors. Any ideas? > > [ 49%]

[jira] [Resolved] (GEODE-2003) Executing a function using REST API fails with full package-qualified name

[ https://issues.apache.org/jira/browse/GEODE-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer resolved GEODE-2003. -- Resolution: Fixed Fix Version/s: 1.1.0 > Executing a function using REST API fails with

[jira] [Commented] (GEODE-2003) Executing a function using REST API fails with full package-qualified name

[ https://issues.apache.org/jira/browse/GEODE-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827106#comment-15827106 ] ASF subversion and git services commented on GEODE-2003: Commit

Re: Review Request 55440: GEODE-1733: Index repository is now created when the chunk bucket becomes primary.

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

Re: Addressing OOM while recovering overflow regions.

Option 1 is not a bad idea. Another thought might be to not start asynchronous value recovery until all of the regions are created. I think right now we launch a task to read all of the oplogs and recover values as soon as the disk store is created. Maybe we could defer that until after the last

Re: Review Request 55591: GEODE-2297: passively discover DistributedSystem instance in AlertAppender

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55591/#review161994 --- I'm closing out this review. I'll need to reimplement

Re: Review Request 55645: GEODE-2293: The AckReaderThread incorrectly shuts down when an IllegalStateException is thrown while releasing an off-heap object

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55645/#review161992 --- Ship it! Ship It! - Barry Oglesby On Jan. 17, 2017, 11:36

Re: Review Request 55532: GEODE-2198: close and re-create the cache on a server when importing new cluster configuration

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

Re: Review Request 55645: GEODE-2293: The AckReaderThread incorrectly shuts down when an IllegalStateException is thrown while releasing an off-heap object

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55645/ --- (Updated Jan. 17, 2017, 11:36 p.m.) Review request for geode and Barry

Re: Review Request 55652: GEODE-2003: REST Function invocation fails on fully qualified Function names

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55652/#review161990 --- Ship it! Ship It! - Hitesh Khamesra On Jan. 17, 2017, 11:25

Re: Addressing OOM while recovering overflow regions.

option 1 looks good to me.. From: Anilkumar Gingade To: dev@geode.apache.org Sent: Tuesday, January 17, 2017 2:41 PM Subject: Addressing OOM while recovering overflow regions. Hi Geode Devs, We are working on ticket GEODE-1672, related to out of memory during

Re: Review Request 55532: GEODE-2198: close and re-create the cache on a server when importing new cluster configuration

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55532/ --- (Updated Jan. 17, 2017, 11:27 p.m.) Review request for geode, Jared Stewart,

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #442 has FAILED (11 tests failed, no failures were new)

--- Spring Data GemFire > Nightly-ApacheGeode > #442 failed (rerun once). --- This build was rerun by John Blum. 11/1614 tests failed, no failures were new.

[jira] [Commented] (GEODE-2306) 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:comment-tabpanel=15827009#comment-15827009 ] ASF GitHub Bot commented on GEODE-2306: --- Github user upthewaterspout commented on the issue:

[GitHub] geode issue #341: GEODE-2306: Update native client BUILDING.md to reflect ch...

Github user upthewaterspout commented on the issue: https://github.com/apache/geode/pull/341 @pivotal-jbarrett - Here's a jira - https://issues.apache.org/jira/browse/GEODE-2317. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub

[jira] [Created] (GEODE-2317) native client cmake build should honor GEODE_HOME environment variable

Dan Smith created GEODE-2317: Summary: native client cmake build should honor GEODE_HOME environment variable Key: GEODE-2317 URL: https://issues.apache.org/jira/browse/GEODE-2317 Project: Geode

[GitHub] geode-examples issue #2: Build updates for examples

Github user upthewaterspout commented on the issue: https://github.com/apache/geode-examples/pull/2 Wowsers, good stuff! A couple of comments/questions: 1. Should we really remove gradlew.bat? That means windows users won't be able to run the examples. 2. Since you are

[GitHub] geode issue #341: GEODE-2306: Update native client BUILDING.md to reflect ch...

Github user pivotal-jbarrett commented on the issue: https://github.com/apache/geode/pull/341 @upthewaterspout, Its an easy change. We went for consistency with the CMake community on the explicit variable setting. It is however consistent to have the module "find" the product by

Re: Jenkins build for geode-examples

I just created a PR with some ideas to consider. IMO, telling users to download unreleased source (such as from our website) would be a problem. Anthony > On Jan 17, 2017, at 2:43 PM, Dan Smith wrote: > > Rat checks are already there for the examples project, but yeah it

[jira] [Commented] (GEODE-2306) 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:comment-tabpanel=15826984#comment-15826984 ] ASF GitHub Bot commented on GEODE-2306: --- Github user upthewaterspout commented on the issue:

Re: Review Request 55644: GEODE-2277 client cache fails to deserialize a PdxInstance due to InternalGemFireError

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55644/#review161982 --- Ship it! OMG!! Did you see the

Re: Jenkins build for geode-examples

Rat checks are already there for the examples project, but yeah it needs a LICENSE and NOTICE. Do those files need to include everything from the geode LICENSE and NOTICE files? That's an interesting question about source archive generation. Do we want to produce releases of the examples, or just

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #441 has FAILED (11 tests failed)

--- Spring Data GemFire > Nightly-ApacheGeode > #441 failed (rerun once). --- This build was rerun by John Blum. 11/1614 tests failed.

Re: Review Request 55440: GEODE-1733: Index repository is now created when the chunk bucket becomes primary.

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

[jira] [Commented] (GEODE-2309) Replace or add ASF copyright statements in source.

[ https://issues.apache.org/jira/browse/GEODE-2309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826950#comment-15826950 ] ASF GitHub Bot commented on GEODE-2309: --- Github user upthewaterspout commented on the issue:

[GitHub] geode issue #342: GEODE-2309: Replace Pivotal Copyright and add Apache Licen...

Github user upthewaterspout commented on the issue: https://github.com/apache/geode/pull/342 Looks good so far, but there are still a lot of files missing apache headers. I don't know how easy it will be to integrate [apache rat](https://creadur.apache.org/rat/) into the cmake build,

Re: Review Request 55532: GEODE-2198: close and re-create the cache on a server when importing new cluster configuration

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55532/ --- (Updated Jan. 17, 2017, 10:21 p.m.) Review request for geode, Jared Stewart,

[jira] [Assigned] (GEODE-2316) Replace GemFire namespace with Geode namespace

[ https://issues.apache.org/jira/browse/GEODE-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dodge reassigned GEODE-2316: Assignee: Michael Dodge > Replace GemFire namespace with Geode namespace >

Re: Review Request 55591: GEODE-2297: passively discover DistributedSystem instance in AlertAppender

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55591/#review161969 --- Enough code knows about AlertAppender that I think you could just

Re: Review Request 55440: GEODE-1733: Index repository is now created when the chunk bucket becomes primary.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55440/ --- (Updated Jan. 17, 2017, 10:09 p.m.) Review request for geode, Barry Oglesby,

Re: [GitHub] geode issue #341: GEODE-2306: Update native client BUILDING.md to reflect ch...

It's current in src/ on next-gen-native-client-software-grant. What do you mean by "down to the root directory"? Sarge > On 17 Jan, 2017, at 13:43, pivotal-jbarrett wrote: > > Github user pivotal-jbarrett commented on the issue: > >

Re: Native Namespace

Anthony, You make a good argument. Have fun converting all those namespaces for us in your free time. :) Apache.Geode.Client and apache::geode::client it is then... Anyone else want to chime in before we execute on this? -Jake On Tue, Jan 17, 2017 at 7:39 AM Anthony Baker

[GitHub] geode issue #341: GEODE-2306: Update native client BUILDING.md to reflect ch...

Github user pivotal-jbarrett commented on the issue: https://github.com/apache/geode/pull/341 Let's also move the BUILDING.md down to the root directory so it is easier to find. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] geode issue #341: GEODE-2306: Update native client BUILDING.md to reflect ch...

Github user pivotal-jbarrett commented on the issue: https://github.com/apache/geode/pull/341 I would suggest a little more detail on the building in windows since the command provided will use NMake and suck for the person building. Include statement about -G generator options.

[jira] [Commented] (GEODE-2309) Replace or add ASF copyright statements in source.

[ https://issues.apache.org/jira/browse/GEODE-2309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826875#comment-15826875 ] ASF GitHub Bot commented on GEODE-2309: --- GitHub user pivotal-jbarrett opened a pull request:

[GitHub] geode pull request #342: GEODE-2309: Replace Pivotal Copyright and add Apach...

GitHub user pivotal-jbarrett opened a pull request: https://github.com/apache/geode/pull/342 GEODE-2309: Replace Pivotal Copyright and add Apache License notice. Can I please get quick review of the copyright and license changes. You can merge this pull request into a Git

Review Request 55644: GEODE-2277 client cache fails to deserialize a PdxInstance due to InternalGemFireError

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55644/ --- Review request for geode, Bruce Schuchardt and Udo Kohlmeyer. Repository:

[jira] [Created] (GEODE-2315) Improve cluster config: starting a second locator which joins a locator with cluster configuration should inherit the first locator's security settings.

Jinmei Liao created GEODE-2315: -- Summary: Improve cluster config: starting a second locator which joins a locator with cluster configuration should inherit the first locator's security settings. Key: GEODE-2315

[jira] [Commented] (GEODE-2198) import cluster-config should continue if the running servers have no data in their application regions

[ https://issues.apache.org/jira/browse/GEODE-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826833#comment-15826833 ] Jinmei Liao commented on GEODE-2198: [~dhardman] I just read your previous comment? Are you saying

[jira] [Commented] (GEODE-2308) Replace GemFire branding with Geode branding.

[ https://issues.apache.org/jira/browse/GEODE-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826834#comment-15826834 ] ASF subversion and git services commented on GEODE-2308: Commit

[jira] [Updated] (GEODE-2314) Assert failure in LuceneQueriesPeerPRRedundancyDUnitTest returnCorrectResultsWhenMoveBucketHappensOnIndexUpdate

[ https://issues.apache.org/jira/browse/GEODE-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nabarun updated GEODE-2314: --- Component/s: lucene > Assert failure in LuceneQueriesPeerPRRedundancyDUnitTest >

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #441 has FAILED (11 tests failed)

--- Spring Data GemFire > Nightly-ApacheGeode > #441 failed. --- This was manually triggered by John Blum. 11/1614 tests failed.

[jira] [Commented] (GEODE-2296) GetFunctionAttribute command is throwing an Anonymouse User Exception

[ https://issues.apache.org/jira/browse/GEODE-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826690#comment-15826690 ] Hitesh Khamesra commented on GEODE-2296: [~jinmeiliao] Should we close this ticket? >

Re: Jenkins build for geode-examples

Also needed: some build work to make this ‘releasable’. For example: LICENSE / NOTICE source archive generation with hashes and sigs rat checks etc Anthony > On Jan 17, 2017, at 10:51 AM, Dan Smith wrote: > > Now that the examples are in a

Re: New Repo for Native Client

I agree with Sarge. I support using the standard tools for each language. I'm inclined to think unification on a single tool can hurt more (e.g. remember ant). And if we don't draw the line in the build process then where will we draw it? I would hate to see more Java code reformatted into C++

Re: New Repo for Native Client

To me this seems related to the question of the degree to which the Geode community should be homogeneous. Who are we trying to attract with the non-Java clients: the existing, Java-centric community or new community members from other platforms? If the former, gradle makes it easy for them to

[jira] [Commented] (GEODE-2260) Move geode examples to new repo home

[ https://issues.apache.org/jira/browse/GEODE-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826511#comment-15826511 ] ASF subversion and git services commented on GEODE-2260: Commit

[jira] [Commented] (GEODE-2313) PulseDataExportTest.dataBrowserExportWorksAsExpected fails with ConditionTimeoutException

[ https://issues.apache.org/jira/browse/GEODE-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826469#comment-15826469 ] ASF subversion and git services commented on GEODE-2313: Commit

Re: New Repo for Native Client

On Mon, Jan 16, 2017 at 8:47 PM, Jacob Barrett wrote: > 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

Re: New Repo for Native Client

As was pointed out by Anthony, the way to go for Native builds is Docker containers. Thanks, Roman. On Tue, Jan 17, 2017 at 7:27 AM, Michael William Dodge wrote: > I know a guy (sadly not part of the Geode community) who has used Jenkins > with gcc. I could probably use him

[jira] [Commented] (GEODE-2031) Host documentation for releases

[ https://issues.apache.org/jira/browse/GEODE-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826437#comment-15826437 ] ASF subversion and git services commented on GEODE-2031: Commit

[jira] [Created] (GEODE-2313) PulseDataExportTest.dataBrowserExportWorksAsExpected fails with ConditionTimeoutException

Kirk Lund created GEODE-2313: Summary: PulseDataExportTest.dataBrowserExportWorksAsExpected fails with ConditionTimeoutException Key: GEODE-2313 URL: https://issues.apache.org/jira/browse/GEODE-2313

[jira] [Commented] (GEODE-2306) 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:comment-tabpanel=15826274#comment-15826274 ] ASF GitHub Bot commented on GEODE-2306: --- Github user PivotalSarge commented on the issue:

[GitHub] geode pull request #341: GEODE-2306: Update native client BUILDING.md to ref...

GitHub user PivotalSarge reopened a pull request: https://github.com/apache/geode/pull/341 GEODE-2306: Update native client BUILDING.md to reflect changes for Geode - Replaced GEMFIRE_HOME with GEODE_ROOT. - Corrected build instructions. - Minor copy-editing. You can merge

[jira] [Commented] (GEODE-2306) 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:comment-tabpanel=15826275#comment-15826275 ] ASF GitHub Bot commented on GEODE-2306: --- GitHub user PivotalSarge reopened a pull request:

[GitHub] geode issue #341: GEODE-2306: Update native client BUILDING.md to reflect ch...

Github user PivotalSarge commented on the issue: https://github.com/apache/geode/pull/341 Mark Doxygen as required and fix typo. --- 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] geode pull request #341: GEODE-2306: Update native client BUILDING.md to ref...

Github user PivotalSarge closed the pull request at: https://github.com/apache/geode/pull/341 --- 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

[jira] [Commented] (GEODE-2306) 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:comment-tabpanel=15826265#comment-15826265 ] ASF GitHub Bot commented on GEODE-2306: --- Github user PivotalSarge closed the pull request at:

[GitHub] geode pull request #341: GEODE-2306: Update native client BUILDING.md to ref...

Github user metatype commented on a diff in the pull request: https://github.com/apache/geode/pull/341#discussion_r96437308 --- Diff: src/BUILDING.md --- @@ -17,7 +22,7 @@ * C++11 compiler *(see platform specific requirements)* ### Optional Tools -* [Doxygen

[jira] [Commented] (GEODE-2306) 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:comment-tabpanel=15826252#comment-15826252 ] ASF GitHub Bot commented on GEODE-2306: --- Github user metatype commented on a diff in the pull

Re: Native Namespace

Based on [1] [2] [3] it seems like the .NET convention would be: Apache.Geode.Client For cpp the conventions seem a lot more muddled [4] [5]. Even for Apache projects [6] [7] [8] [9] there’s lots of variation. This variant looks good to me: apache::geode::client but I could

[jira] [Commented] (GEODE-2306) 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:comment-tabpanel=15826241#comment-15826241 ] ASF GitHub Bot commented on GEODE-2306: --- GitHub user PivotalSarge opened a pull request:

[GitHub] geode pull request #341: GEODE-2306: Update native client BUILDING.md to ref...

GitHub user PivotalSarge opened a pull request: https://github.com/apache/geode/pull/341 GEODE-2306: Update native client BUILDING.md to reflect changes for Geode - Replaced GEMFIRE_HOME with GEODE_ROOT. - Corrected build instructions. - Minor copy-editing. You can merge

Re: Native Namespace

In my experience, it seems easier to have too many namespaces than it is to have too few. My instinct is to start with geode:: and Geode. and further subdivide when it becomes unwieldy and collisions arise. Sarge > On 16 Jan, 2017, at 21:10, Jacob Barrett wrote: > > An

[jira] [Created] (GEODE-2312) Hook rat into cmake build

Anthony Baker created GEODE-2312: Summary: Hook rat into cmake build Key: GEODE-2312 URL: https://issues.apache.org/jira/browse/GEODE-2312 Project: Geode Issue Type: Sub-task

Re: New Repo for Native Client

There was some work done earlier to run the Jenkins jobs in a Docker container. We’re not currently doing that, but I think that’s your best bet to get a stable environment. See https://issues.apache.org/jira/browse/GEODE-60. Anthony > On Jan 16, 2017, at 8:51 PM, Jacob Barrett

RE: docker

Thanks Swapnil. Dor -Original Message- From: Swapnil Bawaskar [mailto:sbawas...@pivotal.io] Sent: יום ג 17 ינואר 2017 11:26 To: dev@geode.apache.org Subject: Re: docker It has been there for a while. You can find it at: https://hub.docker.com/r/apachegeode/geode/ On Tue, Jan 17, 2017

Re: docker

It has been there for a while. You can find it at: https://hub.docker.com/r/apachegeode/geode/ On Tue, Jan 17, 2017 at 12:01 AM, Dor Ben Dov wrote: > Hi, > > Any plans to put Apache Geode in docker hub ? > > Regards, > Dor > This message and the information contained

Re: [ANNOUNCE] Donation of improved GemFire native client

Thanks Jacob. Build goes fine with this change. Thanks Avinash On Tue, Jan 17, 2017 at 5:17 AM, Jacob Barrett wrote: > 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

docker

Hi, Any plans to put Apache Geode in docker hub ? Regards, Dor This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp