Do we expect this to be used by production code or just test code? If this is
going to be used by production code I am concerned with introducing another
singleton class into the mix. We really want to be moving towards a
non-singleton world where I can have more than one Cache in a JVM. For
I look for that myself a while back and couldn’t find anything either.
On Oct 6, 2020, at 4:10 PM, Dale Emery
mailto:dem...@vmware.com>> wrote:
Hi Dan,
I spent more than a week scouring Gradle docs and code for any way to give the
parallel forks their own working directories. I couldn't find
The plan around backwards compatibility makes sense to me.
Anthony
> On Oct 6, 2020, at 4:10 PM, Dale Emery wrote:
>
> Hi Dan,
>
> I spent more than a week scouring Gradle docs and code for any way to give
> the parallel forks their own working directories. I couldn't find a way. At
>
Hi Dan,
I spent more than a week scouring Gradle docs and code for any way to give the
parallel forks their own working directories. I couldn't find a way. At least,
not through the public API. And I'm reluctant to rely on internal APIs, the way
our docker and repeat tests do. If this
+1
Looks good to me. If this is just for tests, I suspect there is some gradle way
to make parallel forks use different working directories. But having this
option in the product doesn't seem like a bad idea.
-Dan
From: Dale Emery
Sent: Tuesday, October 6,
Hi all,
I have submitted an RFC to make Geode’s working directory configurable:
https://cwiki.apache.org/confluence/display/GEODE/Make+Geode%27s+Working+Directory+Configurable
Please review it and comment by Oct 26.
Cheers,
Dale
