We need your help to make the Apache Washington DC Roadshow on Dec 4th a
success.
What do we need most? Speakers!
We're bringing a unique DC flavor to this event by mixing Open Source
Software with talks about Apache projects as well as OSS CyberSecurity,
OSS in Government and and OSS Career
If there’s enough duplication in the lambdas, or in the code around the
lambdas, extracting the duplication into methods would reduce the number of
lambdas.
> On Sep 10, 2018, at 11:03 AM, Kirk Lund wrote:
>
> Alright I'm more up-to-date on this thread. Some things to consider:
>
> The lambda
I think any arguments about what optimizations the (JIT enabled) compiler
(HotSpot or otherwise) will perform at runtime is questionable at best.
HotSpot can "inline" certain [frequent/hot] code paths both at
compile/runtime thereby reducing the number of method invocations (which
also depends on m
Here is AsyncEventListenerDUnitTest that (latest versions of) IntelliJ and
Eclipse both complained exceeded the bytes limit for lambdas:
https://github.com/apache/geode/blob/6ef68c11fdd49e02ded0bfa2bfc072f96f7ab250/geode-core/src/distributedTest/java/org/apache/geode/internal/cache/wan/asyncqueue/
What's the consensus on the version info issue Anthony is calling out? Does
anyone have a proposal for fixing this for this release? Should Nabarun as
the release manager manually correct this for the release and we find a
permanent solution for 1.8?
On Mon, Sep 10, 2018 at 12:33 PM, Anthony Baker
Hi all,
I am looking to add more comprehensive instructions for how to bring Geode
into IntelliJ. I've written the instructions but am now looking at where
to put them.
There appears to be duplicate information in these sections of the Geode
wiki and the README.md/BUILDING.md in the Geode Git re
+1 to revise the wiki to link to README.md/BUILDING.md
On Tue, Sep 11, 2018 at 3:22 PM Ryan McMahon wrote:
> Hi all,
>
> I am looking to add more comprehensive instructions for how to bring Geode
> into IntelliJ. I've written the instructions but am now looking at where
> to put them.
>
> There
---
Spring Data GemFire > Nightly-ApacheGeode > #1037 was successful.
---
Scheduled with changes by John Blum.
2458 tests in total.
https://build.spring.io/brows
I don't care which location (wiki or part of the readme) but I do have
up-to-date instructions that I could update either location with. Maybe a
detailed "Setting up IntelliJ" section on BUILDING.md? Just let me know if
you'd like my version.
On Tue, Sep 11, 2018 at 3:36 PM, Jianxia Chen wrote:
Put it with the source! BUILDING.md or other file.
> On Sep 11, 2018, at 4:11 PM, Kirk Lund wrote:
>
> I don't care which location (wiki or part of the readme) but I do have
> up-to-date instructions that I could update either location with. Maybe a
> detailed "Setting up IntelliJ" section on B
Kirk - I have a PR open here which has the "Setting up IntelliJ" section
you've described:
https://github.com/apache/geode/pull/2456
I would be happy to use your version if you think it is more comprehensive,
or we can revise my PR to include any details you feel are missing.
Ryan
On Tue, Sep 11
Slight clarification—the issue I mentioned is when a user builds Geode from the
source distribution. The source distribution that the release manager creates
has the correct .buildinfo file, it’s just ignored by the build. In short, the
release manager can’t work around the problem.
Does [1]
+1 for putting it into the repo. I am fine with either putting it into
README.md or linking form there.
On Tue, Sep 11, 2018 at 4:33 PM, Ryan McMahon
wrote:
> Kirk - I have a PR open here which has the "Setting up IntelliJ" section
> you've described:
> https://github.com/apache/geode/pull/2456
+1 for the repo as source of truth. Wiki always seemed better as a place to
show examples rather than how to build the project. I also like having the
readme about how to use the product and the building about how to manually
build so one could contribute (especially since Geode already provided
(
14 matches
Mail list logo
