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
omit 2ec7e0134a Minor: Regenerated BOMs for
0116f614ee442bb4379a6afcaccf91651193d35c
add e410c04b1b This workaround isn't needed with hsqldb 2.7.1
add 8872e48f71 Minor: Regenerated BOMs for
0116f614ee442bb4379a6afcaccf91651193d35c
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 (2ec7e0134a)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(8872e48f71)
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:
.../src/main/java/org/apache/openejb/loader/SystemInstance.java | 7 -------
1 file changed, 7 deletions(-)
