This is an automated email from the ASF dual-hosted git repository.
solomax pushed a change to branch spring-6
in repository https://gitbox.apache.org/repos/asf/openmeetings.git
discard df8efe614 [OPENMEETINGS-2756] prometheus is back, code clean-up
discard 384ebc0a9 [OPENMEETINGS-2756] build is green for me; trublemakers so
far: wicket-ioc, prometheus, jackrabbit-webdav
discard cb08b9049 spring is updated
discard fe59ca969 javax.annotation -> jakarta.annotation
discard b8c8800fd Project is compilable, tests are RED
discard 7a033c97f [OPENMEETINGS-2756] spring, cxf, tomcat, wicket
add fdabf606b [OPENMEETINGS-2732] mockito
new af3a45429 [OPENMEETINGS-2756] spring, cxf, tomcat, wicket
new 555bc3684 Project is compilable, tests are RED
new dccb0fc86 javax.annotation -> jakarta.annotation
new 42ce31861 spring is updated
new 489ec99bb [OPENMEETINGS-2756] build is green for me; trublemakers so
far: wicket-ioc, prometheus, jackrabbit-webdav
new 9ddc43753 [OPENMEETINGS-2756] prometheus is back, code clean-up
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 (df8efe614)
\
N -- N -- N refs/heads/spring-6 (9ddc43753)
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.
The 6 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
