Age | Commit message (Collapse) | Author |
|
|
|
|
|
shadowloader treatment. This commit makes it happen.
|
|
|
|
|
|
|
|
Right now the rules are:
* _IF_ a class is being loaded, sourced by a lombok-jar originating class, we FIRST search the lombok jar, and if we can’t find it, farm out the job to the originating equinox-side loader.
* _IF_ the equinox-side loader attempts to load a class, and it does NOT start with lombok, we don’t interfere and would never serve up any content from the lombok-jar (so if we have deps, they do NOT get loaded, by design). If it DOES start with lombok, we load it, and the loading class is SCL, not the equinox-side loader.
* getResource() to load classes did not work (because internally classes end in .SCL.lombok and not .class). This breaks a bunch of things. Fixed by having getResource() be aware that it should try rewriting any request for a .class to .SCL.lombok.
* launchified annotationprocessor, and cleaned up the launchified agent, which now, like all other launchers, just sets up classloader stuff and then calls into the lombok loader side to finish the actual processing, instead of trying to do it itself in a handicapped environment that can’t load much.
|
|
have to solve the problem with adding our shadow loader to the equinox infrastructure (solved in lombok currently by adding all of lombok to the bootclasspath), and all the public API still has to be kept as actual class files by build.xml. Currently it is all shadowed away.
|
|
it is safer to now use the augment class to access that field.
|
|
boolean and references, and the code no longer blows up with a bunch of NPEs if you try to use the reference variant (which is now the only variant) with a primitive type.
Should have zero effect on features or bugs, 100% refactor.
|
|
being broken.
|
|
|
|
|
|
|
|
used a
WeakHashMap to fake a field.
|
|
JDK8 support plugin for Kepler.
|
|
variable' did not work inside for example SneakyThrows-protected methods.
This fix is reverting the change in e835daa9.
During conversion of the internal.ast to the dom AST, a flag is introduced
named 'ORIGINAL'. Commit e835daa9 always explicitly cleared it for
all lombok-generated nodes, in an attempt to try and do the appropriate thing,
treating the ORIGINAL flag as a simile for 'generated code'.
Unfortunately, for eclipse code analysis, all our generated code should be
treated as if it's "really" there, and in general this doesn't work because
eclipse's concept of 'generated' applies to explicit super() calls and the like,
not the kind of stuff lombok introduces.
|
|
transplanted. It shouldn't matter (runPostCompiler will call lombok.jar code, so if there is a classloader issue, transplanting won't help), and roel thinks it might help debug an issue with Springsource gradle plugin for eclipse.
|
|
|
|
|
|
would fail with VerifyError when that code is executed in eclipse.
|
|
org.eclipse.jdt.internal.compiler.lookup.MethodBinding.sourceMethod(MethodBinding.java:1108)
|
|
IllegalArgumentExceptions in certain cases, but with no message, thus making it very hard to figure out what went wrong. The patch throws the same exceptions in the same cases, but gives the exception a useful error message.
|
|
in eclipse for @ExtensionMethod, resulting in VerifyErrors in the emitted class files.
|
|
|
|
this has been fixed
|
|
- Moved Completion proposal code to the PatchExtensionMethodCompletionProposal
class
- Moved out error reporting from EclipseAST.
- Fixed error reporting of the portals.
|
|
the portal itself has lost it's function (Eclipse help is
currently failing, but this also seems to be caused by val).
Major point though is that the Extention methods functionality
works both in javac as in Eclipse.
|
|
|
|
catch(Throwable) instead of catch(Exception). The whole point is to default to an alternative path is anything goes wrong, and it turns out there are various ways to get Throwables instead of Exceptions.
|
|
commits ago).
isGenerated was being transplanted twice, resulting in a ClassFormatError.
NB: This is my fault - transplanting was the only fix I introduced on top of Philipp's work.
|
|
|
|
|
|
getter/setter
|
|
|
|
|
|
|
|
|
|
will use the getter for delegation
|
|
|
|
|
|
errors but I don't think it would work right anyway), and prettied up the error message when you use @Delegate wrong (on static items or methods with args).
Also put back something I accidentally deleted with the previous merge.
|
|
|
|
|
|
2) HandleEqualsAndHashCode now use SetGeneratedByVisitor to ensure "correct" sourcepositions
3) SetGeneratedByVisitor now sets QualifiedNameReference.sourcePositions
|
|
|
|
Issue 316 rename with multiple types II
|
|
|
|
2) Annotations are now handled, but @SuppressWarnings is skipped
|
|
|