This is an automated email from the ASF dual-hosted git repository.
dgriffon pushed a change to branch bump-yauaa
in repository https://gitbox.apache.org/repos/asf/unomi.git
omit 2644d4535 UNOMI-710 : use "java.version" for version check instead of
"java.class.version"
omit 615be1d1d UNOMI-710 : add specific cache for jdk8
omit 1084758e5 UNOMI-710 : bump Yauaa to 7.8.0
add 87c8532d2 UNOMI-717 : set back the setter on personalizations in
context response (#537)
add 608ded728 UNOMI-717: fix retro compatibility for context response
.getPersonali… (#540)
add 84c6efb0f UNOMI-710 : bump Yauaa to 7.8.0
add 9b6993534 UNOMI-710 : add specific cache for jdk8
add 07fb29f59 UNOMI-710 : use "java.version" for version check instead of
"java.class.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 (2644d4535)
\
N -- N -- N refs/heads/bump-yauaa (07fb29f59)
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.
No new revisions were added by this update.
Summary of changes:
api/src/main/java/org/apache/unomi/api/ContextResponse.java | 13 ++++---------
.../apache/unomi/rest/endpoints/ContextJsonEndpoint.java | 2 ++
2 files changed, 6 insertions(+), 9 deletions(-)
