This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regenerate_boms_after_dep_upgrade
in repository https://gitbox.apache.org/repos/asf/tomee.git
discard c4536acfdd Minor: Regenerated BOMs for
8cc02b71c5491fd7d6cdc7423024be10d2f69c2d
add 4a4acbfeda Bump version.openjpa from 4.1.0 to 4.1.1
add e604e1de0a Minor: Regenerated BOMs for
4a4acbfedab81de38100e7f403855f913e7a2050
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 (c4536acfdd)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(e604e1de0a)
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:
examples/alternate-descriptors/pom.xml | 2 +-
examples/multi-jpa-provider-testing/pom.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
