The testrunner now uses a different mechanism to verify correctness of produced errors and warnings (i.e. we intentionally compile code with errors in them to verify that the appropriate error or warning message is emitted when lombok is active during a compilation run of either javac or ecj) - instead of string comparisons, it's a little more complex. This to enable testing of both javac6 and javac7, even if they produce (slightly) different error output.

Updated all message files in the 'expected output' directories to represent this change.
This commit is contained in:
Reinier Zwitserloot committed 2012-10-25 00:07:44 +02:00
1 parent 2d21611898
commit d2808d407a
59 files changed
+320 -208

No files matched your search

@@ -1,8 +1,8 @@
8 warning Not generating isFoo(): A method with that name already exists
14 warning Not generating isFoo(): A method with that name already exists (getFoo)
32 warning Not generating getFoo(): A method with that name already exists
50 warning Not generating getFoo(): A method with that name already exists
62 warning Not generating isFoo(): A method with that name already exists
68 warning Not generating isFoo(): A method with that name already exists (getFoo)
86 warning Not generating getFoo(): A method with that name already exists
104 warning Not generating getFoo(): A method with that name already exists
8:102 Not generating isFoo(): A method with that name already exists
14:186 Not generating isFoo(): A method with that name already exists (getFoo)
32:436 Not generating getFoo(): A method with that name already exists
50:688 Not generating getFoo(): A method with that name already exists
62:868 Not generating isFoo(): A method with that name already exists
68:961 Not generating isFoo(): A method with that name already exists (getFoo)
86:1240 Not generating getFoo(): A method with that name already exists
104:1510 Not generating getFoo(): A method with that name already exists