Adjust 1.6.1 'testRunningBrokenCode_pr102733*' tests ECJ Java 22

Initially, these tests made sure that an old AJC bug causing
incompatibility to ECJ when using `-proceedOnError` was fixed and there
were no regressions. See also:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=102733

Now with the Java 22 changes for JEP 463 "Implicitly Declared Classes
and Instance Main Methods (Second Preview)" in JDT Core, source code is
parsed into a significantly different AST structure than before, even
when using compiler targets < 22. See also https://openjdk.org/jeps/463.

One test has been temporarily adjusted to the byte code created by
ECJ/AJC now.

TODO: Revert/adjust after this upstream bug has been
fixed:
https://github.com/eclipse-jdt/eclipse.jdt.core/issues/2205
Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>

1 files changed, 24 insertions, 0 deletions

diff --git a/tests/bugs161/pr102733/Invoker3.java b/tests/bugs161/pr102733/Invoker3.java
new file mode 100644
index 000000000..e7a0d461e
--- /dev/null
+++ b/tests/bugs161/pr102733/Invoker3.java
@@ -0,0 +1,24 @@
+public class Invoker3 {
+  public static void main(String[] args) throws Throwable {
+    try {
+      C3.main(null);
+    }
+    catch (Throwable t) {
+      boolean failedCorrectly = t.toString().indexOf("Unresolved compilation") != -1;
+      if (failedCorrectly)
+        return;
+      throw new RuntimeException("Call to main should have failed!", t);
+    }
+    try {
+      new C3();
+    }
+    catch (Throwable t) {
+      boolean failedCorrectly =
+        t.toString().contains("Unresolved compilation problem") &&
+          t.toString().contains("blahblahpackage cannot be resolved to a type");
+      if (failedCorrectly)
+        return;
+      throw new RuntimeException("Constructor call should have failed!", t);
+    }
+  }
+}