aboutsummaryrefslogtreecommitdiffstats
path: root/tests/bugs153/GenericMethod/C.java
diff options
context:
space:
mode:
authorAlexander Kriegisch <Alexander@Kriegisch.name>2023-06-04 12:52:54 +0200
committerAlexander Kriegisch <Alexander@Kriegisch.name>2023-06-04 13:01:54 +0200
commit89597d34eec7cab349a1c00a5a2bd85795b9a8f4 (patch)
treeb59349adeb64137f56199a586ddade4389672166 /tests/bugs153/GenericMethod/C.java
parent7fb9f8690c6ec7fe7864cfd79a4f2e45c8f2e6a1 (diff)
downloadaspectj-89597d34eec7cab349a1c00a5a2bd85795b9a8f4.tar.gz
aspectj-89597d34eec7cab349a1c00a5a2bd85795b9a8f4.zip
Fix XML config for Bugs1919Tests.test_GitHub_214
The test started breaking on GitHub, but ran fine locally, which implied some kind of classpath ordering issue. As it turned out, for XML tests all JARs found in the sandbox directory are added to the classpath automatically. So if we do not want them on the classpath, we need to delete or rename them before running. In this case, however, it was enough to make sure the classpath order is correct, so that the duplicate 'Application' class is found in the woven version, not in the unwoven one by chance. We therefore need to use the correct syntax, 1. separating classpath entries by comma, not space, 2. prepending '$sandbox/' to the JAR name. Now the test reliably does what it should have done from the start: run the woven code. Until now, the output assertions were adjusted to the weird result of no aspect logs being present on the console, which was wrong right from the start. Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>
Diffstat (limited to 'tests/bugs153/GenericMethod/C.java')
0 files changed, 0 insertions, 0 deletions