This is an automated email from the ASF dual-hosted git repository. amashenkov pushed a change to branch ignite-13618 in repository https://gitbox.apache.org/repos/asf/ignite-3.git.
discard 7843655 Fix PMD xml schema location. discard 896a3f7 Fix PMD xml schema location. discard 1e45b13 Fix inspections. discard 179cf55 Fix inspections. discard f6bc187 Fix inspections. discard db5fc8b Fix junit engine. discard 5129f95 Styles. discard 4f626e6 Fix junit runner. discard 95cfced Minor. discard f44d6f4 Minor. discard 812cb15 Minor. discard 62bcd20 Minor. discard a369585 Fix inspections. discard 702c3ea Minor. discard b81ac58 Minor. add 3bb05e3 Fix Styles. 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 (7843655) \ N -- N -- N refs/heads/ignite-13618 (3bb05e3) 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: check-rules/pmd-rules.xml | 28 +++++++++++++--------- .../presto/bytecode/DumpBytecodeVisitor.java | 1 - parent/pom.xml | 12 +++++----- 3 files changed, 23 insertions(+), 18 deletions(-)