This is an automated email from the ASF dual-hosted git repository.
udo pushed a change to branch feature/GEODE-5660
in repository https://gitbox.apache.org/repos/asf/geode.git.
omit ca0ee71 GEODE-5660: updating war files in test not to collide with
current geode-web-api.war already on classpath
omit de11332 GEODE-5660: spotless
omit cdff940 GEODE-5660: Updated AgentUtilJUnitTest.java to use
`findWarLocation` method. Cleaned up the AgentUtil.java logic to determine path
locations
omit 4121388 GEODE-5660: Added method to lookup war file from classpath
within AgentUtil.java. This is to address problem where http server is started
from Java API (Spring Data Geode specifically) Now, the application can
reference the `geode-web-api` war from repo and not have to specifically set
`GEODE-HOME` property
new b24c94f GEODE-5660: Added method to lookup war file from classpath
within AgentUtil.java. This is to address problem where http server is started
from Java API (Spring Data Geode specifically) Now, the application can
reference the `geode-web-api` war from repo and not have to specifically set
`GEODE-HOME` property
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (ca0ee71)
\
N -- N -- N refs/heads/feature/GEODE-5660 (b24c94f)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
