Reinier Zwitserloot d2808d407a 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.

2012-10-25 00:07:44 +02:00

..

after-delombok

test for using 'val' on an expression that involved lombok-generated code.

2012-08-13 00:11:22 +02:00

after-ecj

test for using 'val' on an expression that involved lombok-generated code.

2012-08-13 00:11:22 +02:00

before

test for using 'val' on an expression that involved lombok-generated code.

2012-08-13 00:11:22 +02:00

messages-delombok

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.

2012-10-25 00:07:44 +02:00

messages-ecj

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.

2012-10-25 00:07:44 +02:00

messages-idempotent

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.

2012-10-25 00:07:44 +02:00