On Sat, 15 Mar 2003 04:07, Korosh Afshar wrote:
> It seems Log4JLoggerManager in excalibur-logger-1.0.jar was the culprit
> which was using antiquated Category.
I updated everything in Phoenix HEAD and hopefully all version incompatability
has gone.
> incidently on startup using:
>
> <logs version="log4j">
> <appender name="FILE" class="org.apache.log4j.FileAppender">
> <param name="File" value="foo.txt"/>
> <param name="Append" value="false"/>
> <layout class="org.apache.log4j.PatternLayout">
> <param name="ConversionPattern" value="%p - %m%n"/>
> </layout>
> </appender>
> <root>
> <priority value="debug"/>
> <appender-ref ref="FILE"/>
> </root>
> </logs>
>
> results in foo.txt ending up in the PHONEIX_HOME/foo.txt directory and
> not the PHOENIX_HOME/apps/MyApp/foo.txt directory.
Looks to be relative to the working directory. In the Logkit log format you
can use variables such as ${app.dir} to set logs relative to. Unfortunatly
this is not available in log4j configuration.
We could probably preprocess the file before we passed it to log4j and
interpret the variables (possibly treating it as a jelly script). However
thats something we can do in the future.
Could you add this to the bugboard at;
http://jira.codehaus.org/secure/BrowseProject.jspa?id=10081
--
Cheers,
Peter Donald
---------------------------------------------------
"Therefore it can be said that victorious warriors
win first, and then go to battle, while defeated
warriors go to battle first, and then seek to win."
- Sun Tzu, the Art Of War
---------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
