 Reinier Zwitserloot
|
89f98da78d
|
[fixes #678] @Synchronize an instance method on static variable no longer emits a warning.
|
2020-02-14 01:21:24 +01:00 |
|
|
Roel Spilker
|
bad93ae677
|
Only look at the line number for errors and warnings.
|
2013-08-19 23:50:57 +02:00 |
|
|
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 |
|
|
Reinier Zwitserloot
|
fe4985e212
|
Added setting position of generated nodes in javac's @Synchronized as a 'pilot' to see if we cause any problems with this approach. It does generate nicer error messages!
Example: Using @Synchronized with named lock on a static method, naming a non-existent or instance lock. That used to error on line -1.
|
2012-07-16 22:51:56 +02:00 |
|
|
Reinier Zwitserloot
|
e642150998
|
Updated tests to reflect changes to delombok (delombok now kills super(), because attrib adds them even in places where that's wrong).
Also split up the SynchronizedName test into separate cases for each expected failure mode.
|
2012-07-16 22:04:39 +02:00 |
|