(for those who didn't see the commit msg:) I've modified the chainsaw.jar target to not fail when the ORO jar is not present.
If the location of the ORO jar is not provided in build.properties, a warning message is displayed and the task continues. The chainsaw jar is created, excluding (because they rely on ORO): LikeRule LogFilePatternReceiver ------------------------------------------------ Other build/code organization issues: ExpressionFilter and rule package ExpressionFilter is currently available only from the Chainsaw jar, although it's not used by Chainsaw at all. It's a filter (used with appenders) which provides access to the same rules and expression syntax used to colorize and filter events in Chainsaw. The rules package (org.apache.log4j.rule) is used by ExpressionFilter as well as Chainsaw, but is currently available only from the Chainsaw jar. The expression syntax and rules package provide access to all parts of a logging event through keywords, as well as support for: operators: ==, !=, EXISTS, <, <=, >, >=, LIKE (regexp), ~= (case-insensitive partial text match) grouping of expressions using boolean operators &&, ||, ! and parentheses For example, to filter only expressions with the word 'result' or 'timing' in the message, use this expression: MSG ~= 'result' || MSG ~= 'timing' Is there interest in moving these files (ExpressionFilter and the rule package) from the chainsaw jar to the core jar? They provide a great amount of flexibility in filtering and I've been working recently to make sure their performance is on-par with the existing filters in the sandbox. Thoughts?
<<winmail.dat>>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
