Anthony said: ... > Nathan said: > > if you're really looking for something to dig into, the current > > configuration issue (hard-coded, non-overwritable logger and resource > > loader) might be a good one for you. i've looked at it a bit, and > > i've yet > > to see a clean solution for it. if you want to take a shot, i think > > that'd > > be great place to start. > > Could you give me a little better direction than this? Are you talking > about issues with the stand-alone Velocity or the Tools?
i was referring to the "Known Issues/Bugs" section in the STATUS document for the tools subproject. in particular, the first listed "issue." if you're interested in digging into this, the first place you'll want to look is in the initVelocity() method of the VelocityViewServlet. there the velocity.properties file is loaded and the log system and resource loader are explicitly set (in hard-coded fashion, regardless of the velocity.properties that were loaded). this is not really a "showstopper," and if it ends up requiring some more drastic changes, i may be willing to support a 1.0 release without dealing with this. but, we need to at least take a shot at it. Nathan Bubna [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
