This is an automated email from the ASF dual-hosted git repository. michaelo pushed a change to branch SUREFIRE-2251 in repository https://gitbox.apache.org/repos/asf/maven-surefire.git
discard 103151d95 [SUREFIRE-2251] [REGRESSION] java.lang.NoSuchMethodException: org.apache.maven.plugin.surefire.StartupReportConfiguration.<init> add daa011b85 Bump org.assertj:assertj-core from 3.26.0 to 3.26.3 add a93783a63 [SUREFIRE-2251] [REGRESSION] java.lang.NoSuchMethodException: org.apache.maven.plugin.surefire.StartupReportConfiguration.<init> 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 (103151d95) \ N -- N -- N refs/heads/SUREFIRE-2251 (a93783a63) 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: pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)