diff options
author | Reinier Zwitserloot <r.zwitserloot@projectlombok.org> | 2020-08-29 04:14:10 +0200 |
---|---|---|
committer | Reinier Zwitserloot <r.zwitserloot@projectlombok.org> | 2020-08-29 04:14:10 +0200 |
commit | 9148294f78a8e646ee131ca182a9b692bc028fdb (patch) | |
tree | e6815bec55b6de0a09db125ea65a5166e31ecb57 /src/core/lombok/SneakyThrows.java | |
parent | 7e44900cd3c22bb038ec07383d33cf5b7ae17c55 (diff) | |
download | lombok-9148294f78a8e646ee131ca182a9b692bc028fdb.tar.gz lombok-9148294f78a8e646ee131ca182a9b692bc028fdb.tar.bz2 lombok-9148294f78a8e646ee131ca182a9b692bc028fdb.zip |
[testing] [eclipse] [#2413] Eclipse tests now more expansive
We now test generating a level2-DOM from our level1-AST (eclipse has 3 levels of ASTs, more or less), only if
that is possible, i.e. only if the full eclipse is available. This requires using a test target named `eclipse-X`, and not
one of the `ecjX` ones. This is the change that requires the massive update to the build system. About 6 tests,
including a newly added one about @Delegate, now fail. These failures would usually not cause instant failure in
eclipse, but can cause errors during save actions and will likely mess with other things in weird ways, such as
messing up syntax highlighting.
Yes, this commit now makes a bunch of cases fail the unit tests, but that is representative of actual errors in lombok,
so I'm checking it in as is (without this commit, the problem is still there, the tests are just incapable of detecting it).
Diffstat (limited to 'src/core/lombok/SneakyThrows.java')
0 files changed, 0 insertions, 0 deletions