A) Geode-all-bom contains the dependency versions for our projects.
B) maybe not needed, since the dependencies nate already present...
On Tue, Mar 26, 2019, 16:09 Anthony Baker wrote:
> I’m curious:
>
> - Why do all subprojects declare a dependency on
> project(':boms:geode-all-bom’)) ?
> - Why
I’m curious:
- Why do all subprojects declare a dependency on
project(':boms:geode-all-bom’)) ?
- Why are we shipping geode-all-bom-1.9.0.jar in the lib/ dir and in our war
files?
Thanks,
Anthony
Are you sure it's not necessary to do a clean build when switching between
different branches? Especially branches that are far enough apart in
revisions that their gradle build files are different? Sometimes two
branches, such as for two different releases, are significantly different
in the gradl
Hi Bill,
You should have access now.
-Dan
On Tue, Mar 26, 2019 at 3:06 PM Bill Burcham wrote:
> I need edit access to https://cwiki.apache.org for:
>
> bill.burc...@gmail.com
>
> The immediate need is to update some UML here:
>
> https://cwiki.apache.org/confluence/display/GEODE/HA+Client+Even
I need edit access to https://cwiki.apache.org for:
bill.burc...@gmail.com
The immediate need is to update some UML here:
https://cwiki.apache.org/confluence/display/GEODE/HA+Client+Event+Queues
Thanks!
As Dan mentioned, the few times I've seen this has been a result of running
clean in the same build set as spotless. While that "shouldn't" be an
issue, it seems to be the underlying cause.
I encourage you to not clean every time you build. We've done a lot of
work lately to improve the correctn
Cool! Thanks Jake!
--
Mike Stolz
Principal Engineer, GemFire Product Lead
Mobile: +1-631-835-4771
On Tue, Mar 26, 2019 at 2:42 PM Jacob Barrett wrote:
>
>
> > On Mar 26, 2019, at 11:26 AM, Michael Stolz wrote:
> >
> > I may be mistaken, but I think that this feature attempts to address
> cas
I actually have two lines in my gradle.properties. The combo seems to make
spotless behave when it gets into the broken state I mentioned before:
org.gradle.daemon=false
org.gradle.parallel=false
This does make it slower but slower is better than broken.
On Tue, Mar 26, 2019 at 11:38 AM Kirk Lun
> On Mar 26, 2019, at 11:26 AM, Michael Stolz wrote:
>
> I may be mistaken, but I think that this feature attempts to address cases
> where users want to selectively copy several items from one distributed
> system to another. Not sure if the two separate implementations of
> "ClientCache"
I just had this occur again. And I found another solution, albeit not a
great one, but if you disable org.gradle.daemon that also clears up this
problem. You can add this to ~/.gradle/gradle.properties:
org.gradle.daemon=false
Just to clarify, I'm on a Mac using gradlew in geode (I don't have my
I may be mistaken, but I think that this feature attempts to address cases
where users want to selectively copy several items from one distributed system
to another. Not sure if the two separate implementations of "ClientCache"
actually achieves the same thing. Would like to discuss though.
>
Perhaps for others on this list that aren’t familiar with the context you could
fill in the blanks.
It is assumed you are asking about the “feature” where PDX metadata is
propagated from one connection pool to another in an attempt to support
multiple distributed systems in the same client. Whi
Few more details that might help others...
Each Geode module fails in the same way but obviously on a different .java
file, and I have not altered these .java files -- they do not appear to
have any format issues involving imports.
Once gradle is in this state, switching branches from a feature b
I have had several issues running clean in combination with other gradle
commands - I think because of our parallel build. Maybe do this?
$ ./gradlew clean; ./gradlew build -xtest
On Tue, Mar 26, 2019 at 10:43 AM Kirk Lund wrote:
> Intermittent build error caused by spotlessJava. My checkout of
Intermittent build error caused by spotlessJava. My checkout of Geode
intermittently gets into a state that then fails to build. I've been seeing
this come and go for the last month or two. I'm not sure what puts it into
this state but executing:
$ ./gradlew clean build -x test
...will repeatedly
Yes. From our experiment that looked like a possibility.
-Anil.
On Tue, Mar 26, 2019 at 9:59 AM Dan Smith wrote:
> Following up on the conflation thing - Anil and I did an experiment.
> Conflation definitely *does* happen on everything in the queue, not just
> the last batch. But we didn't see
Following up on the conflation thing - Anil and I did an experiment.
Conflation definitely *does* happen on everything in the queue, not just
the last batch. But we didn't see destroys get conflated with updates.
So one thing that might make this use case work is to conflate the destroys
with the
Thanks. I'm happy to hear that.
--
Mike Stolz
Principal Engineer, GemFire Product Lead
Mobile: +1-631-835-4771
On Tue, Mar 26, 2019, 12:46 PM Blake Bender wrote:
> Okay, after a conversation here at the office with folks who know, I can
> confirm the answer is "yes," NC has code to copy PDX ty
Okay, after a conversation here at the office with folks who know, I can
confirm the answer is "yes," NC has code to copy PDX types in the manner
you're asking after.
Thanks,
Blake
On Tue, Mar 26, 2019 at 8:43 AM Blake Bender wrote:
> Hi Mike,
>
> I'm not 100% certain what you're referring to
Hi Mike,
I'm not 100% certain what you're referring to, but... PdxSerializable in NC
has toData and fromData methods that allow you to copy objects via
serialization. That what you're looking for?
Thanks,
Blake
On Mon, Mar 25, 2019 at 12:53 PM Michael Stolz wrote:
> Does this functionality
I've been thinking along those lines as well Suranjan. Since conflation
and expiry-forwarding don't solve the problem of running out of disk
space the solution needs to involve the dispatch thread.
For the session-state caching scenario that raised this whole issue I
think what you've describ
Hi,
Can you tell me why is this header removed from geode native public API
(https://issues.apache.org/jira/browse/GEODE-3421),
and how we can use XA transactions (2PC) in geode native?
BR,
Mario
22 matches
Mail list logo
