Registering for IBM's bloatware is not something I can commit to :(
I'm stumped as to why you get absolutely nothing, not even errors,
even though evidently lombok.jar is being loaded. The fact that
eclipsec.exe is not giving you anything is normal; nothing in eclipse
is supposed to print to standard output (though lombok will in certain
situations).
I'm not sure where to go from here. You could grab the sources from
the git repository (just run 'ant installDeps' and then 'ant dist' to
make a distro, this should work on any system so long as you have a
1.6 JVM and ant installed, no other dependencies), and start
debugging. The entry point you're most likely looking for is the
EclipsePatcher class.
You can check if lombok actually ends up fixing any eclipse classes by
adding -Dlombok.patcher.debugDir=C:/some/existing/but/empty/directory
in the -vmargs set (in eclipse.ini together with -bootclasspath and
friends). Files that get patched are copied as a file there. If you
don't see any files, then, nothing is getting patched.
If you some files there, that would be interesting information. If you
see absolutely nothing there, you'll have to mess with the
lombok.patcher project (it's standalone from lombok itself). Look at
the ScriptManager class, which hosts a ClassFileTransformer. Stick
some debug prints in there. *every* *single* class loaded by the VM
passes through here, so if you System.out.println every call into it,
your eclipse will take about a minute or 2 to start up, and there'll
be a continuous stream of classnames in your console window, so you
may want to be a bit more discerning and check if anything that starts
with "org/eclipse/jdt/" is flying by. If yes, that would also be
interesting. If no, then either RAD is not using eclipse's JDT at all,
in which case, that will be the end of the line (as far as lombok is
concerned, RAD would be an entirely new IDE with all the complexity
inherent in that for adding lombok support to it), _OR_ RAD is loading
the jdt parts in an entirely separate VM (that'd be very weird,
especially considering that you do see lombok entries in your
configuration details), which you can test by checking your processes.
On Dec 15, 3:02 pm, Steve <
stara...@gmail.com> wrote:
> Well, let's see...
>
> ** I know eclipse.ini is being picked up. If I introduce a syntax
> error into that file, RAD/Eclipse vomits when it starts.
> ** In any case, I took the stuff from eclipse.ini and put it all in
> one whopping long command line to launch. Exact same results.
> ** I launched with eclipsec.exe and the console window was shown.
> However, nothing at all was ever displayed in it. Same thing when I
> eclipsec.exe on plain old Eclipse 3.5.x. Not sure what I was supposed
> to see, but an empty console window didn't seem to be telling me much!
> ** I know the Lombok vmargs are being picked up. When I do a Help/
> About/Configuration Details (I think this is a RAD-specific thing) I
> see references to lombok.jar as expected.
> ** I tried running Lombok on RAD 7.5.4 on a different machine with the
> same results. Slightly different platform (WinXp/32 vs my Win7/64),
> but the base RAD 7.5.4 is identical.
> ** Probably a worthless data point, by Lombok also works perfectly
> fine in the MyEclipse 8.0 Blue Edition.
>
> Very stumped. I'd really like to get this working!
>
> If you have the energy to dig into this further, you can download a
> free trial of RAD fromhttp://
www.ibm.com/developerworks/downloads/r/rad/?S_TACT=105AGX15&S_...