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 ------- Additional Comments From [EMAIL PROTECTED] 2003-09-04 13:28 ------- The current behaviour for cocoon.xconf location is quite complex - it hunts for it. For our purposes, if it is relative, it will try first relative to the context dir. If it is absolute, it'll use it as an absolute path. So both behaviours are available. However, surely relative paths are much more important, as absolute ones in config files pin those config files down to a specific system, which isn't always good. So we need to be able to handle _both_ absolute and relative paths, and have them always handled in the same way in all situations (i.e. cocoon.xconf, logkit.xconf, etc) This scopes the requirements further than my original fix, which is why I rolled back for now. Upayavira
