> Good idea. I have some aspect code for tracing. I don't want to move > toward aspectj for a while. It is sort of a pain. I'd rather get the > package more stable, then remove some of the tracing and then use more > aspectj over the next month or so.
Well, I'd already started with aspectj. It shouldn't have to be hard, I want to get it seamlessly integrated with the build process. I agree that getting it more stable should be the first priority, but since I don't yet have a good handle on what problems need fixing, working on logging, documentation, and tests is useful for me. And good clean logging helps me (and I suspect others) to understand and trust the package. Same for documentation =] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
