[PROPOSAL]: Finer Grained Security When Invoking Methods in OQL

Hello all, The current approach used to authorize methods during OQL execution seems to be way too restrictive, I've drafted a proposal to change the current behavior and allow further customization: https://cwiki.apache.org/confluence/display/GEODE/Customizable+Security+When+Invoking+Methods+in+O

Re: [PROPOSAL]: Finer Grained Security When Invoking Methods in OQL

Juan, Nice work - you've obviously given this plenty of thought. I'm not qualified to comment on the technical aspects of your proposal, but as a proofreader I noticed that there are a couple of occurrences of "invokation" that should be spelled "invocation". Dave On Mon, Jun 25, 2018 at 2:52 AM

Re: [PROPOSAL]: Finer Grained Security When Invoking Methods in OQL

Hello Dave, Thanks for the heads up, spelling errors fixed (at least that one :-/). Cheers!. On Mon, Jun 25, 2018 at 4:34 PM Dave Barnes wrote: > Juan, > Nice work - you've obviously given this plenty of thought. I'm not > qualified to comment on the technical aspects of your proposal, but as

Compilation errors in IntelliJ

Intellij should now build geode just fine with the default gradle settings as of 226e406. If you followed these instructions to uncheck "Create separate modules per source" to get things working last week you might want to reimport the gradle project with the default settings. -Dan On Thu, Jun

Re: Compilation errors in IntelliJ

I've pulled, done a clean build, recreated my IntelliJ project and still see this compilation error in buildSrc: /Users/klund/dev/gemfire_CLEAN/open/buildSrc/src/test/ java/org/apache/geode/javac/TestCompiler.java Error:(40, 23) java: cannot find symbol symbol: class EnsureCorrectRunsWithProce

Re: Compilation errors in IntelliJ

I'm also seeing two problems on the command-line. 1) occasionally a build (without tests) will hang in one the compile targets and 2) I just started seeing occasional out of memory errors building with gradle (see below). *> Task :geode-lucene:compileTestJava* The system is out of resources. C

Geode unit tests completed in 'develop/AcceptanceTest' with non-zero exit code

Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/AcceptanceTest/builds/115

Geode unit tests completed in 'develop/UITests' with non-zero exit code

Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/UITests/builds/116

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

--- Spring Data GemFire > Nightly-ApacheGeode > #959 was successful. --- Scheduled 2425 tests in total. https://build.spring.io/browse/SGF-NAG-959/ -- This

Re: Compilation errors in IntelliJ

After upgrading from JDK 1.8.0_152 to 1.8.0_172, I think my command-line builds are behaving better. Next IntelliJ failure was https://intellij-support.jetbrains.com/hc/en-us/community/posts/36162670-In-2018-1-1-version-Problem-with-Error-cannot-start-process-the-working-directory-idea-modules

Build failed in Jenkins: Geode-nightly #1236

See Changes: [github] GEODE-4791: Fix intellij with gradle 4.8 by removing provided [github] Write a test that hangs without the fix for GEODE-3563. (#2057) [github] GEODE-4511: rework ClientAuthDUnitRule to illus

Spring Boot for Apache Geode 1.0.0.M1 Released!

Apache Geode Community- It is my please to announce the first milestone release of Spring Boot for Apache Geode, version 1.0.0.M1. See the official Spring Blog Post [1] for more details. Documentation [2] is available as are a couple of Examples [3]. Feedback appreciated and welcomed. Much mor

Geode unit tests 'develop/DistributedTest' took too long to execute

Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/79