handling Shadow.PreInitialization as a INITIALIZER_RELATION

rather than printing a warning message to System.err

this fixes the dirty output that was very visible when running the
harness with -emacssym enabled

diff --git a/weaver/src/org/aspectj/weaver/AsmAdaptor.java b/weaver/src/org/aspectj/weaver/AsmAdaptor.java
index ba84390f978e77e3e03173f1c806ada91bdcd116..15e94274ecebaa5ab568c7fe11b6e8a345181fb2 100644 (file)
--- a/weaver/src/org/aspectj/weaver/AsmAdaptor.java
+++ b/weaver/src/org/aspectj/weaver/AsmAdaptor.java
@@ -53,6 +53,9 @@ public class AsmAdaptor {
                                relation = AdviceAssociation.METHOD_RELATION;
                        } else if (shadow.getKind().equals(Shadow.ConstructorExecution)) {
                                relation = AdviceAssociation.CONSTRUCTOR_RELATION;
+                       } else if (shadow.getKind().equals(Shadow.PreInitialization)) {
+                               // TODO: someone should check that this behaves reasonably in the IDEs
+                               relation = AdviceAssociation.INITIALIZER_RELATION;
                        } else {
                                System.err.println("> unmatched relation: " + shadow.getKind());
                                relation = AdviceAssociation.METHOD_RELATION;