This is an automated email from the ASF dual-hosted git repository.
jungm pushed a change to branch BVAL-222
in repository https://gitbox.apache.org/repos/asf/bval.git
discard 08f8bd0 BVAL222 - enable BValInterceptor when constraints are only
placed on parent classes
discard 7ebd079 BVAL222 - Add unit test
add 52d30a2 Bump org.apache.felix:maven-bundle-plugin from 5.1.9 to 6.0.0
add b057062 Bump org.apache.maven.plugins:maven-javadoc-plugin from
3.11.1 to 3.11.2
add 9395d1b Bump version.tomcat from 11.0.1 to 11.0.2
add cad22eb Bump owb.version from 4.0.2 to 4.0.3
add af4aacc Bump org.hibernate:hibernate-validator from 8.0.1.Final to
8.0.2.Final
add d2af1ce Bump org.mockito:mockito-core from 5.14.2 to 5.15.2
add 806c486 Merge pull request #174 from
apache/dependabot/maven/org.mockito-mockito-core-5.15.2
add 760a6b4 disable persisted credentials in gh-action
add cabcef0 BVAL222 - Add unit test
add 31ce8b5 BVAL222 - enable BValInterceptor when constraints are only
placed on parent classes
add 445cff1 fix owb version after rebase
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 (08f8bd0)
\
N -- N -- N refs/heads/BVAL-222 (445cff1)
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:
.github/workflows/bval-ci.yml | 3 +++
bval-perf/pom.xml | 2 +-
pom.xml | 10 +++++-----
3 files changed, 9 insertions(+), 6 deletions(-)
