[MNG-8670] Fix concurrent builder missing/wrong project events

[oehme]

Rather than adding another test, I've expanded on the one I previously
wrote for ProjectStarted events.

---

https://issues.apache.org/jira/browse/MNG-8670

[cstamas]

Source formatting issues make ITs fail. @oehme

[cstamas]

Cool! JIRA mentions ProjectSkipped, does it mean we lack other events as well?

[INFO] Running org.apache.maven.it.MavenITmng8648ProjectEventsTest
Error:  Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.916 s <<< FAILURE! -- in org.apache.maven.it.MavenITmng8648ProjectEventsTest
Error:  org.apache.maven.it.MavenITmng8648ProjectEventsTest.test -- Time elapsed: 1.914 s <<< ERROR!
org.apache.maven.it.VerificationException: Text not found in log: org.apache.maven.its.mng8648:root:pom:1-SNAPSHOT ProjectSucceeded
	at org.apache.maven.it.Verifier.verifyTextInLog(Verifier.java:445)
	at org.apache.maven.it.MavenITmng8648ProjectEventsTest.test(MavenITmng8648ProjectEventsTest.java:52)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)

[oehme]

The reason I mentioned ProjectSkipped was because the root project is listed as "Skipped" on the command line when using the concurrent builder, but gets no event. However, when I run this with the traditional builder, the root project is marked as "Successful" instead and gets a success event. I created the test with this behavior as my template.

I don't really mind which way you go (mark it as skipped or mark it as successful), as long as it gets an event :)

For project-d, the behavior is similarly inconsistent. It gets no events at all with the old builder and it is marked as "successful" with the new builder, which seems wrong, since it depends on a failed project.

[jira-importer]

Resolve #9636