diff options
| author | Alexander Kriegisch <Alexander@Kriegisch.name> | 2022-03-01 11:31:17 +0700 |
|---|---|---|
| committer | Alexander Kriegisch <Alexander@Kriegisch.name> | 2022-03-23 15:39:14 +0700 |
| commit | e18c4f92938b117eaea32a340ea1ba65fa0585ae (patch) | |
| tree | c1c3ecedc417c1b1b699306b026df2e2198de1b2 /tests/src/test/resources/org/aspectj/systemtest | |
| parent | 9d35aceab5f642c8d8eaa59ddae4ed2c66a081ed (diff) | |
| download | aspectj-e18c4f92938b117eaea32a340ea1ba65fa0585ae.tar.gz aspectj-e18c4f92938b117eaea32a340ea1ba65fa0585ae.zip | |
Name annotation vs native style aspects uniformly in github_128 tests
Trying to find the difference between byte code generated by AJC for
functionally identical annotation vs native style aspect, I move the
aspects into subdirectories in order to be able to name them
identically. This way, when decompiling them with javap or Fernflower it
is easier to diff them later.
Why the decompilation? Because for the thread pool testing scenario
native syntax passes while annotation syntax fails. I.e., we need to
find the difference. That can be done by reading source code, if you
know where to look, or by starting with reverse engineering in order to
first understand more and look at the code later.
Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>
Diffstat (limited to 'tests/src/test/resources/org/aspectj/systemtest')
| -rw-r--r-- | tests/src/test/resources/org/aspectj/systemtest/ajc198/ajc198.xml | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/tests/src/test/resources/org/aspectj/systemtest/ajc198/ajc198.xml b/tests/src/test/resources/org/aspectj/systemtest/ajc198/ajc198.xml index 0e1132782..25f5692f2 100644 --- a/tests/src/test/resources/org/aspectj/systemtest/ajc198/ajc198.xml +++ b/tests/src/test/resources/org/aspectj/systemtest/ajc198/ajc198.xml @@ -168,7 +168,7 @@ </ajc-test> <ajc-test dir="bugs198/github_128" title="asynchronous proceed for nested around-advice (@AspectJ)"> - <compile files="Application.java MarkerA.java MarkerAAspect.aj MarkerB.java MarkerBAspect.aj" options="-1.8" /> + <compile files="Application.java MarkerA.java MarkerB.java annotation_syntax/MarkerAAspect.aj annotation_syntax/MarkerBAspect.aj" options="-1.8" /> <run class="Application" options="1,1"> <stdout ordered="no"> <line text=">> Outer intercept"/> @@ -247,7 +247,7 @@ </ajc-test> <ajc-test dir="bugs198/github_128" title="asynchronous proceed for nested around-advice (@AspectJ, thread pool)"> - <compile files="Application.java MarkerA.java MarkerAAspect.aj MarkerB.java MarkerBAspect.aj" options="-1.8" /> + <compile files="Application.java MarkerA.java MarkerB.java annotation_syntax/MarkerAAspect.aj annotation_syntax/MarkerBAspect.aj" options="-1.8" /> <run class="Application" options="1,1,true"> <stdout ordered="no"> <line text=">> Outer intercept"/> @@ -326,7 +326,7 @@ </ajc-test> <ajc-test dir="bugs198/github_128" title="asynchronous proceed for nested around-advice (native)"> - <compile files="Application.java MarkerA.java MarkerANativeAspect.aj MarkerB.java MarkerBNativeAspect.aj" options="-1.8" /> + <compile files="Application.java MarkerA.java MarkerB.java native_syntax/MarkerAAspect.aj native_syntax/MarkerBAspect.aj" options="-1.8" /> <run class="Application" options="1,1"> <stdout ordered="no"> <line text=">> Outer intercept"/> @@ -405,7 +405,7 @@ </ajc-test> <ajc-test dir="bugs198/github_128" title="asynchronous proceed for nested around-advice (native, thread pool)"> - <compile files="Application.java MarkerA.java MarkerANativeAspect.aj MarkerB.java MarkerBNativeAspect.aj" options="-1.8" /> + <compile files="Application.java MarkerA.java MarkerB.java native_syntax/MarkerAAspect.aj native_syntax/MarkerBAspect.aj" options="-1.8" /> <run class="Application" options="1,1,true"> <stdout ordered="no"> <line text=">> Outer intercept"/> |