1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
|
<!DOCTYPE suite SYSTEM "../tests/ajcTestSuite.dtd"[]>
<!--
Java 20: no new final language features, only preview/incubator ones:
- "JEP 432: Record Patterns (Second Preview)" (###)
- "JEP 433: Pattern Matching for switch (Fourth Preview)" (###)
- "JEP 429: Scoped Values (Incubator)" (API only)
- "JEP 436: Virtual Threads (Second Preview)" (API only)
- "JEP 437: Structured Concurrency (Second Incubator)" (API only)
-->
<suite>
<!-- Java ?? final, Java 17, 18, 19, 20 preview -->
<ajc-test dir="features1920/java20" vm="20" title="switch pattern matching preview 4 java">
<compile files="SwitchPatternPreview4OK.java" options="--enable-preview -20" />
<run class="SwitchPatternPreview4OK" vmargs="--enable-preview">
<message></message>
<stdout>
<line text="null" />
<line text="int 123" />
<line text="long 999" />
<line text="double 12.340000" />
<line text="String foo" />
<line text="[123, foo, 999, 12.34]" />
<line text="Non-circle" />
<line text="Small circle" />
<line text="Large circle" />
<line text="Sealed sub-class A" />
<line text="Sealed sub-class B" />
<line text="Sealed sub-record C" />
<line text="absolute value 1: -1" />
<line text="other integer: 0" />
<line text="positive integer: 42" />
<line text="other integer: -99" />
<line text="positive integer: 123" />
<line text="value unavailable: null" />
</stdout>
</run>
</ajc-test>
<!-- Java ?? final, Java 17, 18, 19, 20 preview -->
<ajc-test dir="features1920/java20" vm="20" title="switch pattern matching preview 4 error">
<compile files="SwitchPatternPreview4Error.java" options="--enable-preview -20">
<!-- TODO: Add correct compiler error message, as soon as JDT Core supports it -->
<message kind="error" file="SwitchPatternPreview4Error.java" text="This case label is dominated by one of the preceding case labels"/>
</compile>
</ajc-test>
<!-- Java ?? final, Java 17, 18, 19, 20 preview -->
<ajc-test dir="features1919/java19" vm="20" title="switch pattern matching preview 3 aspect">
<compile files="SwitchPatternPreview3Aspect.aj" options="--enable-preview -20" />
<run class="Application" vmargs="--enable-preview">
<stdout>
<line text="null" />
<line text="int 123" />
<line text="long 999" />
<line text="double 12.340000" />
<line text="String foo" />
<line text="[123, foo, 999, 12.34]" />
<line text="Non-circle" />
<line text="Small circle" />
<line text="Large circle" />
<line text="Sealed sub-class A" />
<line text="Sealed sub-class B" />
<line text="Sealed sub-record C" />
<line text="absolute value 1: -1" />
<line text="other integer: 0" />
<line text="positive integer: 42" />
<line text="other integer: -99" />
<line text="positive integer: 123" />
<line text="value unavailable: null" />
</stdout>
</run>
</ajc-test>
<!-- Java ?? final, Java 17, 18, 19, 20 preview -->
<ajc-test dir="features198/java17" vm="20" title="switch pattern matching error">
<compile files="SwitchPatternError.java" options="--enable-preview -20">
<!-- TODO: Add correct compiler error message, as soon as JDT Core supports it -->
<message kind="error" file="SwitchPatternError.java" text="This case label is dominated by one of the preceding case labels"/>
</compile>
</ajc-test>
<!-- Java ?? final, Java 17, 18, 19, 20 preview -->
<ajc-test dir="features1919/java19" vm="20" title="switch pattern matching preview 3 error 1">
<compile files="SwitchPatternPreview3Error1.java" options="--enable-preview -20">
<!-- TODO: Add correct compiler error message, as soon as JDT Core supports it -->
<message kind="error" file="SwitchPatternPreview3Error1.java" text="This case label is dominated by one of the preceding case labels"/>
</compile>
</ajc-test>
<!-- Java ?? final, Java 17, 18, 19, 20 preview -->
<ajc-test dir="features1919/java19" vm="20" title="switch pattern matching preview 3 error 2">
<compile files="SwitchPatternPreview3Error2.java" options="--enable-preview -20">
<!-- TODO: Add correct compiler error message, as soon as JDT Core supports it -->
<message kind="error" file="SwitchPatternPreview3Error2.java" text="This case label is dominated by one of the preceding case labels"/>
</compile>
</ajc-test>
<!-- Java ?? final, Java 19, 20 preview -->
<ajc-test dir="features1919/java19" vm="20" title="record patterns">
<compile files="RecordPatternsPreview1OK.java" options="--enable-preview -20"/>
</ajc-test>
<!-- Java ?? final, Java 19, 20 preview -->
<ajc-test dir="features1919/java19" vm="20" title="record patterns error">
<compile files="RecordPatternsPreview1Error.java" options="--enable-preview -20">
<!-- https://github.com/eclipse-jdt/eclipse.jdt.core/issues/450 (fixed for preview 2 in Eclipse 2033-03, 4.27) -->
<!--
<message kind="error" file="RecordPatternsPreview1Error.java" text="Raw types are not allowed in record patterns"/>
<message kind="error" file="RecordPatternsPreview1Error.java" text="Raw types are not allowed in record patterns"/>
-->
</compile>
<run class="RecordPatternsPreview1Error" vmargs="--enable-preview">
<stdout>
<line text="I'm a box"/>
<line text="I'm a box"/>
</stdout>
</run>
</ajc-test>
<!-- Java ?? final, Java 19, 20 preview -->
<ajc-test dir="features1919/java19" vm="20" title="record patterns exhaustiveness 1">
<compile files="RecordPatternsPreview1ExhaustivenessOK1.java" options="--enable-preview -20"/>
<run class="RecordPatternsPreview1ExhaustivenessOK1" vmargs="--enable-preview">
<stdout>
<line text="y"/>
<line text="a"/>
</stdout>
</run>
</ajc-test>
<!-- Java ?? final, Java 19, 20 preview -->
<ajc-test dir="features1919/java19" vm="20" title="record patterns exhaustiveness aspect">
<compile files="RecordPatternsPreview1ExhaustivenessAspect.aj" options="--enable-preview -20"/>
<!-- TODO: Remove redundant default clauses when https://github.com/eclipse-jdt/eclipse.jdt.core/issues/455 has been fixed -->
<run class="RecordPatternsPreview1ExhaustivenessAspect" vmargs="--enable-preview">
<stdout>
<line text="y"/>
<line text="a"/>
<line text="Pair[x=C@000, y=D@000]"/>
</stdout>
</run>
</ajc-test>
<!-- Java ?? final, Java 19, 20 preview -->
<ajc-test dir="features1919/java19" vm="20" title="record patterns aspect">
<compile files="RecordPatternsPreview1Aspect.aj" options="--enable-preview -20"/>
<run class="RecordPatternsPreview1Aspect" vmargs="--enable-preview">
<stdout>
<line text="9"/>
<line text="14"/>
<line text="Doing something with Point[x=2, y=7]"/>
<line text="Upper-left color: RED"/>
<line text="Upper-left color: RED"/>
<line text="Upper-left x coordinate: 1"/>
<line text="Doing something with Rectangle[upperLeft=ColoredPoint[p=Point[x=1, y=6], c=RED], lowerRight=ColoredPoint[p=Point[x=4, y=6], c=BLUE]]"/>
</stdout>
</run>
</ajc-test>
<!-- Java ?? final, Java 19, 20 preview -->
<ajc-test dir="features1919/java19" vm="20" title="record patterns exhaustiveness error">
<compile files="RecordPatternsPreview1ExhaustivenessError.java" options="--enable-preview -20">
<message kind="error" file="RecordPatternsPreview1ExhaustivenessError.java" text="An enhanced switch statement should be exhaustive; a default label expected"/>
</compile>
</ajc-test>
<!-- Java ?? final, Java 19, 20 preview -->
<ajc-test dir="features1919/java19" vm="20" title="record patterns exhaustiveness 2">
<compile files="RecordPatternsPreview1ExhaustivenessOK2.java" options="--enable-preview -20"/>
<run class="RecordPatternsPreview1ExhaustivenessOK2" vmargs="--enable-preview">
<stdout>
<line text="Bob 12"/>
</stdout>
</run>
</ajc-test>
<!-- RuntimeException in BcelWeaver, see https://github.com/eclipse/org.aspectj/issues/190 -->
<ajc-test dir="bugs1920/github_190" vm="1.5" title="switch with Integer.MAX_VALUE case">
<compile files="SwitchCaseWith_Integer_MAX_VALUE.java" options="-1.5 -showWeaveInfo">
<message kind="weave" text="Join point 'method-execution(java.lang.String SwitchCaseWith_Integer_MAX_VALUE.switchTest(int))'"/>
</compile>
<run class="SwitchCaseWith_Integer_MAX_VALUE">
<stdout>
<line text="execution(String SwitchCaseWith_Integer_MAX_VALUE.switchTest(int))"/>
<line text="CASE_1"/>
</stdout>
</run>
</ajc-test>
<!--
'Syntax error, insert "Expression" to complete Expression' when compiling parenthesised expressions
containing AspectJ keywords, e.g. '(before)', see https://github.com/eclipse/org.aspectj/issues/20
-->
<ajc-test dir="bugs1920/github_20" vm="1.5" title="parenthesised expression with AspectJ keyword">
<compile files="ParenthesisedAJKeywords.java" options="-1.5 -showWeaveInfo"/>
<run class="ParenthesisedAJKeywords">
<stdout>
<line text="before"/>
<line text="after"/>
<line text="around"/>
<line text="aspect"/>
<line text="pointcut"/>
<line text="declare"/>
<line text="privileged"/>
</stdout>
</run>
</ajc-test>
<!--
'inner aspects must be static' when compiling an interface with an inner aspect which was not explicitly declared
static, see https://github.com/eclipse/org.aspectj/issues/162
-->
<ajc-test dir="bugs1920/github_162" vm="1.5" title="inner aspect of interface is implicitly static">
<compile files="InterfaceWithInnerClass.java" options="-1.5 -showWeaveInfo">
<message kind="weave" text="method-execution(int InterfaceWithInnerClass$ImplicitlyStatic.getNumber())' in Type 'InterfaceWithInnerClass$ImplicitlyStatic'"/>
<message kind="weave" text="method-execution(void InterfaceWithInnerClass$ImplicitlyStatic.main(java.lang.String[]))' in Type 'InterfaceWithInnerClass$ImplicitlyStatic'"/>
</compile>
<run class="InterfaceWithInnerClass$ImplicitlyStatic">
<stdout>
<line text="execution(void InterfaceWithInnerClass.ImplicitlyStatic.main(String[]))"/>
<line text="execution(int InterfaceWithInnerClass.ImplicitlyStatic.getNumber())"/>
<line text="11"/>
</stdout>
</run>
</ajc-test>
<!--
When compiling aspect and target class together, matching works as expected,
see https://github.com/eclipse/org.aspectj/issues/24
-->
<ajc-test dir="bugs1920/github_24" vm="1.5" title="exact array type matching, aspect compiled together with target class">
<compile files="ExactlyMatchingAspect.aj MaybeMissingClass.java" options="-1.5 -showWeaveInfo">
<!-- Even before the bugfix, in this case weaving worked as expected -->
<message kind="weave" text="method-execution(MaybeMissingClass MaybeMissingClass.f1())"/>
<message kind="weave" text="method-execution(MaybeMissingClass[] MaybeMissingClass.f2())"/>
<message kind="weave" text="method-execution(MaybeMissingClass[][] MaybeMissingClass.f3())"/>
<message kind="weave" text="method-execution(int MaybeMissingClass.f4())"/>
<message kind="weave" text="method-execution(int[] MaybeMissingClass.f5())"/>
<message kind="weave" text="method-execution(int[][] MaybeMissingClass.f6())"/>
</compile>
<run class="MaybeMissingClass">
<stdout>
<line text="MaybeMissingClass.f1"/>
<line text="execution(MaybeMissingClass MaybeMissingClass.f1())"/>
<line text="MaybeMissingClass.f2"/>
<line text="execution(MaybeMissingClass[] MaybeMissingClass.f2())"/>
<line text="MaybeMissingClass.f3"/>
<line text="execution(MaybeMissingClass[][] MaybeMissingClass.f3())"/>
<line text="MaybeMissingClass.f4"/>
<line text="execution(int MaybeMissingClass.f4())"/>
<line text="MaybeMissingClass.f5"/>
<line text="execution(int[] MaybeMissingClass.f5())"/>
<line text="MaybeMissingClass.f6"/>
<line text="execution(int[][] MaybeMissingClass.f6())"/>
</stdout>
</run>
</ajc-test>
<!--
When compiling aspect and target class separately, too many joinpoints are matched,
see https://github.com/eclipse/org.aspectj/issues/24
-->
<ajc-test dir="bugs1920/github_24" vm="1.5" title="exact array type matching, aspect compiled separately from target class">
<compile files="ExactlyMatchingAspect.aj" options="-1.5 -showWeaveInfo" outjar="aspect.jar">
<message kind="warning" text="no match for this type name: MaybeMissingClass [Xlint:invalidAbsoluteTypeName]"/>
<message kind="warning" text="advice defined in ExactlyMatchingAspect has not been applied [Xlint:adviceDidNotMatch]"/>
</compile>
<compile files="MaybeMissingClass.java" options="-1.5 -showWeaveInfo" aspectpath="aspect.jar">
<!-- Before the bugfix, f1 would be woven twice, f2 not at all-->
<message kind="weave" text="method-execution(MaybeMissingClass MaybeMissingClass.f1())"/>
<message kind="weave" text="method-execution(MaybeMissingClass[] MaybeMissingClass.f2())"/>
<message kind="weave" text="method-execution(MaybeMissingClass[][] MaybeMissingClass.f3())"/>
<message kind="weave" text="method-execution(int MaybeMissingClass.f4())"/>
<message kind="weave" text="method-execution(int[] MaybeMissingClass.f5())"/>
<message kind="weave" text="method-execution(int[][] MaybeMissingClass.f6())"/>
</compile>
<run class="MaybeMissingClass" classpath="aspect.jar">
<stdout>
<line text="MaybeMissingClass.f1"/>
<line text="execution(MaybeMissingClass MaybeMissingClass.f1())"/>
<line text="MaybeMissingClass.f2"/>
<line text="execution(MaybeMissingClass[] MaybeMissingClass.f2())"/>
<line text="MaybeMissingClass.f3"/>
<line text="execution(MaybeMissingClass[][] MaybeMissingClass.f3())"/>
<line text="MaybeMissingClass.f4"/>
<line text="execution(int MaybeMissingClass.f4())"/>
<line text="MaybeMissingClass.f5"/>
<line text="execution(int[] MaybeMissingClass.f5())"/>
<line text="MaybeMissingClass.f6"/>
<line text="execution(int[][] MaybeMissingClass.f6())"/>
</stdout>
</run>
</ajc-test>
<!--
When compiling aspect and target class together, too many joinpoints are matched,
see https://github.com/eclipse/org.aspectj/issues/24
-->
<ajc-test dir="bugs1920/github_24" vm="1.5" title="fuzzy array type matching, aspect compiled together with target class">
<compile files="FuzzilyMatchingAspect.aj MaybeMissingClass.java" options="-1.5 -showWeaveInfo">
<!-- Before the bugfix, both f1 and f2 would be woven twice -->
<message kind="weave" text="method-execution(MaybeMissingClass MaybeMissingClass.f1())"/>
<message kind="weave" text="method-execution(MaybeMissingClass[] MaybeMissingClass.f2())"/>
<message kind="weave" text="method-execution(MaybeMissingClass[][] MaybeMissingClass.f3())"/>
<message kind="weave" text="method-execution(int MaybeMissingClass.f4())"/>
<message kind="weave" text="method-execution(int[] MaybeMissingClass.f5())"/>
<message kind="weave" text="method-execution(int[][] MaybeMissingClass.f6())"/>
</compile>
<run class="MaybeMissingClass">
<stdout>
<line text="MaybeMissingClass.f1"/>
<line text="execution(MaybeMissingClass MaybeMissingClass.f1())"/>
<line text="MaybeMissingClass.f2"/>
<line text="execution(MaybeMissingClass[] MaybeMissingClass.f2())"/>
<line text="MaybeMissingClass.f3"/>
<line text="execution(MaybeMissingClass[][] MaybeMissingClass.f3())"/>
<line text="MaybeMissingClass.f4"/>
<line text="execution(int MaybeMissingClass.f4())"/>
<line text="MaybeMissingClass.f5"/>
<line text="execution(int[] MaybeMissingClass.f5())"/>
<line text="MaybeMissingClass.f6"/>
<line text="execution(int[][] MaybeMissingClass.f6())"/>
</stdout>
</run>
</ajc-test>
<!--
When compiling aspect and target class separately, too many joinpoints are matched,
see https://github.com/eclipse/org.aspectj/issues/24
-->
<ajc-test dir="bugs1920/github_24" vm="1.5" title="fuzzy array type matching, aspect compiled separately from target class">
<compile files="FuzzilyMatchingAspect.aj" options="-1.5 -showWeaveInfo" outjar="aspect.jar">
<message kind="warning" text="advice defined in FuzzilyMatchingAspect has not been applied [Xlint:adviceDidNotMatch]"/>
</compile>
<compile files="MaybeMissingClass.java" options="-1.5 -showWeaveInfo" aspectpath="aspect.jar">
<!-- Before the bugfix, both f1 and f2 would be woven twice -->
<message kind="weave" text="method-execution(MaybeMissingClass MaybeMissingClass.f1())"/>
<message kind="weave" text="method-execution(MaybeMissingClass[] MaybeMissingClass.f2())"/>
<message kind="weave" text="method-execution(MaybeMissingClass[][] MaybeMissingClass.f3())"/>
<message kind="weave" text="method-execution(int MaybeMissingClass.f4())"/>
<message kind="weave" text="method-execution(int[] MaybeMissingClass.f5())"/>
<message kind="weave" text="method-execution(int[][] MaybeMissingClass.f6())"/>
</compile>
<run class="MaybeMissingClass" classpath="aspect.jar">
<stdout>
<line text="MaybeMissingClass.f1"/>
<line text="execution(MaybeMissingClass MaybeMissingClass.f1())"/>
<line text="MaybeMissingClass.f2"/>
<line text="execution(MaybeMissingClass[] MaybeMissingClass.f2())"/>
<line text="MaybeMissingClass.f3"/>
<line text="execution(MaybeMissingClass[][] MaybeMissingClass.f3())"/>
<line text="MaybeMissingClass.f4"/>
<line text="execution(int MaybeMissingClass.f4())"/>
<line text="MaybeMissingClass.f5"/>
<line text="execution(int[] MaybeMissingClass.f5())"/>
<line text="MaybeMissingClass.f6"/>
<line text="execution(int[][] MaybeMissingClass.f6())"/>
</stdout>
</run>
</ajc-test>
<!--
https://github.com/eclipse/org.aspectj/issues/214
https://github.com/mojohaus/aspectj-maven-plugin/issues/164
Problem with multiple, subsequent weaving steps and '-Xlint:warning' or '-Xlint:unorderedAdviceAtShadow=warning'
java.lang.ArrayIndexOutOfBoundsException: 1
[ERROR] at org.aspectj.weaver.bcel.BcelShadow.prepareForMungers(BcelShadow.java:379)
[ERROR] at org.aspectj.weaver.Shadow.implement(Shadow.java:546)
-->
<ajc-test dir="bugs1920/github_214" vm="1.5" title="ArrayIndexOutOfBoundsException with Xlint unorderedAdviceAtShadow=warning">
<compile files="FirstAspect.java MarkerOne.java" options="-1.8 -showWeaveInfo -Xlint:warning" outjar="first-aspect.jar">
<message kind="warning" text="can not build thisJoinPoint lazily for this advice since it has no suitable guard [Xlint:noGuardForLazyTjp]"/>
<message kind="warning" text="advice defined in FirstAspect has not been applied [Xlint:adviceDidNotMatch]"/>
</compile>
<compile files="Application.java MarkerTwo.java" options="-1.5 -showWeaveInfo -Xlint:warning" classpath="$sandbox/first-aspect.jar" outjar="application.jar"/>
<compile files="SecondAspect.java" options="-1.5 -showWeaveInfo -Xlint:warning" aspectpath="first-aspect.jar" inpath="application.jar" outjar="second-aspect.jar">
<message kind="warning" text="can not build thisJoinPoint lazily for this advice since it has no suitable guard [Xlint:noGuardForLazyTjp]"/>
<message kind="warning" text="at this shadow method-execution(void Application.greet(java.lang.String)) no precedence is specified between advice applying from aspect FirstAspect and aspect SecondAspect [Xlint:unorderedAdviceAtShadow]"/>
<message kind="warning" text="can not implement lazyTjp at joinpoint method-execution(void Application.greet(java.lang.String)) because of advice conflicts, see secondary locations to find conflicting advice [Xlint:multipleAdviceStoppingLazyTjp]"/>
<message kind="weave" text="method-execution(void Application.greet(java.lang.String))' in Type 'Application' (Application.java:4) advised by around advice from 'SecondAspect'"/>
<message kind="weave" text="method-execution(void Application.greet(java.lang.String))' in Type 'Application' (Application.java:4) advised by before advice from 'FirstAspect'"/>
</compile>
<run class="Application" classpath="$sandbox/second-aspect.jar,$sandbox/first-aspect.jar">
<stdout>
<line text="FirstAspect: execution(void Application.greet(String))"/>
<line text="SecondAspect: execution(void Application.greet(String))"/>
<line text="Hello world!"/>
</stdout>
</run>
</ajc-test>
<!-- https://github.com/eclipse-aspectj/aspectj/issues/246 -->
<ajc-test dir="bugs1920/github_246" vm="8" title="add correct annotations to multiple ITD methods with the same name and same number of arguments">
<compile files="First.java Second.java App.java ITDAspect.aj" options="-8"/>
<run class="App">
<stdout>
<line text="[@Second()] public int App.foo(int[])"/>
<line text="[@First()] public void App.foo(java.lang.String)"/>
<line text="[] public void App.foo(java.lang.String[])"/>
<line text="[@First(), @Second()] public void App.foo(java.lang.Object)"/>
<line text="[@Second()] public int App.foo(int)"/>
</stdout>
</run>
</ajc-test>
<!-- https://github.com/eclipse-aspectj/aspectj/issues/250 -->
<ajc-test dir="bugs1920/github_250" vm="8" title="correctly handle overloaded private methods in aspects">
<compile files="MyAspect.aj" options="-8"/>
<run class="MyAspect">
<stdout>
<line text="execution(void Application.doSomething())"/>
<line text="1 / one"/>
<line text="execution(void Application.doSomething())"/>
<line text="2"/>
</stdout>
</run>
</ajc-test>
</suite>
|
