accessing a project's properties file in a lombok handler?

[Ray Vanderborght]

I added support for java.util.logging to morbok's @Logger recently (with slf4j coming next) and it occurred to me that I really want to allow externalizing the configuration into a properties file in the project's classpath.

So instead of doing this for every non-log4j @Logger enabled class:

@Logger(type=Logger.Type.JAVA)

you could just specify vanilla @Logger and let the properties file dictate which logger type gets generated.  Unfortunately I can't get the handler to find the properties file... perhaps because of some classloader isolation going on.  I took a few shot-in-the-dark attempts but no luck so far.  Am I dreaming that this could be doable?  The commented out section of my eclipse handler below shows the general idea:

http://code.google.com/p/morbok/source/browse/trunk/morbok/src/lombok/eclipse/handlers/HandleLogger.java?spec=svn18&r=18

Thanks,

Ray

--
http://www.bartendr.com

[Reinier Zwitserloot]

Well, in order to support compile-time type reflection, which you'd need for @Delegate, closures, and about half the features we cook up, you need access to the local concept of the filer - the thing that you can ask questions like:

This code mentions "List" - um, what's that referring to, and what methods does this 'List' thingie have?

In javac, we pretty much already have access. In eclipse, it's slightly more complicated as we hook at an earlier level, but we need to go here anyway. Once we code in access to the filer within lombok, then using it to find a properties file that is in the source and/or classpath should be a trivial exercise. Until then, though...

--Reinier Zwitserloot

[Ray Vanderborght]

Good to know, thanks.

--
http://www.bartendr.com