Can't rely on the ones built as part of the AspectJ build as the weaver test cases are sensitive to the exact compiler used (needs to be Eclipse 2.1.1 based).

il y a 20 ans · 49f9e52d6f
--- a/weaver/testdata/bin/Aspect.class
+++ b/weaver/testdata/bin/Aspect.class
--- a/weaver/testdata/bin/DynamicHelloWorld.class
+++ b/weaver/testdata/bin/DynamicHelloWorld.class
--- a/weaver/testdata/bin/FancyHelloWorld.class
+++ b/weaver/testdata/bin/FancyHelloWorld.class
--- a/weaver/testdata/bin/FieldyHelloWorld.class
+++ b/weaver/testdata/bin/FieldyHelloWorld.class
--- a/weaver/testdata/bin/HelloWorld.class
+++ b/weaver/testdata/bin/HelloWorld.class
--- a/weaver/testdata/bin/MultiArgHelloWorld.class
+++ b/weaver/testdata/bin/MultiArgHelloWorld.class
--- a/weaver/testdata/bin/README.txt
+++ b/weaver/testdata/bin/README.txt
@@ -0,0 +1,4 @@
 The class files in this directory are an *input* to the weaver tests. They were generated
 from the .java files in testsrc using an Eclipse 2.1.1 compiler (well, ajc actually). The
 weaver tests are sensitive to implementation details in class file output that vary by compiler.
 When we rev. the jdt.core to 3.0.0 these class files will need to be updated again.
--- a/weaver/testdata/bin/Test.class
+++ b/weaver/testdata/bin/Test.class
--- a/weaver/testdata/bin/TestSwitchy.class
+++ b/weaver/testdata/bin/TestSwitchy.class