DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22916>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22916 Full path for logkit.xconf location fail [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From [EMAIL PROTECTED] 2003-09-04 11:43 ------- This was actually an intentional change. All other files (e.g. cocoon.xconf) are referred to relative to the context directory (specified in <context-dir/> in cli.xconf). But the logkit file is specified relative to the invocation context (in this case whereever Ant was started). This is why it was changed. Are you saying that you want to be able to specify your logkit file as an absolute path? If so, the CLI should (a) happily accept absolute paths on all filenames and (b) assume the context-directory when relative paths are specified. If this makes sense, it shouldn't be hard to implement. However, for the time being I have returned the CLI back to its original behaviour, and added a better behaviour to my todo list. Upayavira
