Kirk and I tracked this down. He had a GEODE_HOME environment variable
which the locator was picking up and finding an old war file from.
-Dan
On Fri, Nov 1, 2019 at 4:16 PM Dan Smith wrote:
> Hi Kirk,
>
> Did you do a ./gradlew clean? It looks like you might be picking up an old
> version of o
I filed https://issues.apache.org/jira/browse/GEODE-7403 and I'm currently
trying to:
a) determine if it reproduces in both CLI and IntelliJ (IntelliJ so far
with a clean checkout of develop)
b) determine why an error-level log message logged by the background dunit
locator is not causing a LogCon
Kirk, will you craft a Jira about this for the "Build" component, and
assign it to me?
On Mon, Nov 4, 2019, 09:30 Kirk Lund wrote:
> If it is picking up an old version of geode then it's doing so because we
> use old versions for upgrade/backwards testing. The only old versions of
> the jars I h
If it is picking up an old version of geode then it's doing so because we
use old versions for upgrade/backwards testing. The only old versions of
the jars I have are the ones that our build pulls down for the upgrade
tests. These old versions do tend confuse intellij so it's possible it's a
proble
Hi Kirk,
Did you do a ./gradlew clean? It looks like you might be picking up an old
version of one of the geode war files that is referring to the old location
of the LogService class.
-Dan
On Fri, Nov 1, 2019 at 3:28 PM Kirk Lund wrote:
> To reproduce, drop this new test in geode-dunit/src/di
