This is an automated email from the ASF dual-hosted git repository.
jsinovassinnaik pushed a change to branch UNOMI-821
in repository https://gitbox.apache.org/repos/asf/unomi.git
discard 7e3e6ab6c upgrade version
omit 4924b58a5 update CI to only use JDK11 for master branch
omit e44d60b92 use a version of org.json built with jdk8
omit 10c12adc9 UNOMI-821: upgrade org.json version
add b5e61141d UNOMI-822: add search json schema (#658)
new 91e4eb212 UNOMI-821: upgrade org.json version
new 2879bad8d use a version of org.json built with jdk8
new 0cf5d9fd1 update CI to only use JDK11 for master branch
new 27a1f3bf1 upgrade version
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 (7e3e6ab6c)
\
N -- N -- N refs/heads/UNOMI-821 (27a1f3bf1)
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 4 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:
.../{click/click.json => search/search.json} | 12 +++++++---
.../schemas/events/search/search.properties.json | 28 ++++++++++++++++++++++
2 files changed, 37 insertions(+), 3 deletions(-)
copy
extensions/json-schema/services/src/main/resources/META-INF/cxs/schemas/events/{click/click.json
=> search/search.json} (60%)
create mode 100644
extensions/json-schema/services/src/main/resources/META-INF/cxs/schemas/events/search/search.properties.json
