Summary: | ExpressionFilter backport | ||
---|---|---|---|
Product: | Log4j - Now in Jira | Reporter: | Curt Arnold <carnold> |
Component: | Other | Assignee: | log4j-dev <log4j-dev> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | ||
Priority: | P2 | ||
Version: | 1.3alpha | ||
Target Milestone: | --- | ||
Hardware: | Other | ||
OS: | other |
Description
Curt Arnold
2007-04-12 07:04:17 UTC
Should be functional at the writing. Can be checked out from: svn co https://svn.apache.org/repos/asf/logging/sandbox/log4j/expression-filter Maven build will use log4j-1.2.14.jar (which it will download if it hasn't already). Put a recent Maven 2 on path and do: mvn package : to build jar mvn site : to build documentation mvn install : to add to local Maven repo Committed changes in rev 566357 that migrates the ExpressionFilter from Jakarta ORO to java.util.regex that was introduced in JDK 1.4. The change should be transparent unless you used pattern delimiters in filters like: MSG LIKE /.*foo/ instead of just writing: MSG LIKE .*foo If that level of compatibility is needed, identical bracketing characters could be detected and the rule could return true if either the straight pattern or the pattern with bracketing characters removed matched the field. However, since ExpressionFilter was introduced in log4j 1.3, I don't feel the need for that level of compatibility unless it that was known to be used in the field. Feedback appreciated. |