I was building the log4j-sandbox against the latest log4j source and
noticed that some files that have made the move to log4j proper haven't
been removed from log4j-sandbox. One is the LevelMatchFilter and there are
a few others that nearly match class names and are probably the same. We
shou
hoju2005/01/04 22:00:03
Modified:..cvsignore
Log:
add bin directory to .cvsignore (for Eclipse purposes)
Revision ChangesPath
1.14 +2 -1 logging-log4j/.cvsignore
Index: .cvsignore
===
Hi Mark,
Look in the logging-log4j-sandbox. However, you'll have to check it out
with the tag "LOG4J_SANDBOX_ALPHA3". The HEAD is currently compatible with
Log4j-1.3 (at least last I checked, which has been few weeks now).
Jake
At 05:25 PM 1/4/2005 -0800, you wrote:
>Is there a version of Cont
> No, log4j objects will not be referenced as Component. It is not a
> marker interface either.
>
> The requirement to have both Component as an interface and
> ComponentBase as a class, stems from the fact that we make the
> distinction between Appender the interface and AppenderSkeleton the
> cl
Is there a version of ContextJNDISelector that is compatible with log4j
1.2.8 or 1.2.9? What are folks using for a RepositorySelector in the
pre-1.3 world?
-Mark
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
Hi all, Long shot, but I'll be in London from Monday10th-Friday14th for
a flying work-thing. Should there be any log4j related folks in that
area that are up for a drink, let me know.
cheers,
Paul Smith
-
To unsubscribe, e-mai
Web start:
http://logging.apache.org/log4j/docs/webstart/chainsaw/chainsawWebStart.jnlp
Zip bundle
http://logging.apache.org/log4j/docs/webstart/chainsaw/chainsaw-bundle.zip
Any problems, let me know, I'm still getting used to my new Mac laptop
so there may well be something...
cheers,
Paul Smith
psmith 2005/01/04 13:47:32
Modified:.build.xml
Log:
UGLI classes were not being included in the jar, which caused Chainsaw to
fail to start
for me at least via the Webstart distro.
Revision ChangesPath
1.129 +3 -1 logging-log4j/build.xml
Index: bui
The requirement to have both Component as an interface and
ComponentBase as a class, stems from the fact that we make the
distinction between Appender the interface and AppenderSkeleton the
class. Implementations of Appender derive from AppenderSkeleton but
all the other code in log4j refers to Ap
ceki2005/01/04 12:23:41
Modified:src/java/org/apache/log4j/plugins PluginSkeleton.java
Receiver.java
Log:
PluginSkeletin extends ComponentBase
Revision ChangesPath
1.11 +2 -3
logging-log4j/src/java/org/apache/log4j/plugins/PluginSkel
Hello Scott,
Since we have the possibility of configuring sub-components of
components, the expression parameter should be added to instances of
the appropriate TriggeringEventEvaluator. Once of the reasons behind
the development of Joran was to address the problem of configuring
sub-components of
At 06:27 PM 1/4/2005, Mark Womack wrote:
Not a bad idea per se, but what is the motivation with making it an
interface? Will the outside world need to know about the Component
interface in any way? Do we intend to reference log4j objects as Component
or maybe use it as a marker interface?
No, log
ceki2005/01/04 11:56:51
Modified:src/java/org/apache/log4j/net SMTPAppender.java
Log:
Corrections to SMTPAppender
Revision ChangesPath
1.43 +3 -2
logging-log4j/src/java/org/apache/log4j/net/SMTPAppender.java
Index: SMTPAppender.java
=
ceki2005/01/04 11:48:48
Modified:src/java/org/apache/log4j/or RendererMap.java
Log:
Log4j components now see their owning LR.
Revision ChangesPath
1.14 +14 -18
logging-log4j/src/java/org/apache/log4j/or/RendererMap.java
Index: RendererMap.java
ceki2005/01/04 11:48:37
Modified:src/java/org/apache/log4j/joran JoranConfigurator.java
Log:
Log4j components now see their owning LR.
Revision ChangesPath
1.31 +4 -4
logging-log4j/src/java/org/apache/log4j/joran/JoranConfigurator.java
Index: JoranConf
ceki2005/01/04 11:48:29
Modified:src/java/org/apache/log4j/joran/action PluginAction.java
AppenderAction.java LevelAction.java
LayoutAction.java
src/java/org/apache/log4j/filter LevelMatchFilter.java
Log:
Log4j compon
ceki2005/01/04 11:42:12
Modified:tests/src/java/org/apache/log4j/pattern
PatternParserTest.java
src/java/org/apache/log4j/rolling
FixedWindowRollingPolicy.java
src/java/org/apache/joran/helper SimpleRuleSto
ceki2005/01/04 09:58:50
Removed: examples/src/jmx T.java
Log:
JMX code has been moved to logging-log4j-attic
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
ceki2005/01/04 09:58:05
Removed: src/java/org/apache/log4j/jmx package.html
HierarchyDynamicMBean.java LoggerDynamicMBean.java
AppenderDynamicMBean.java Agent.java
LayoutDynamicMBean.java MethodUnion.java
Not a bad idea per se, but what is the motivation with making it an
interface? Will the outside world need to know about the Component
interface in any way? Do we intend to reference log4j objects as Component
or maybe use it as a marker interface?
If we just need this internally for log4j then
ceki2005/01/04 08:19:28
Modified:src/java/org/apache/log4j PropertyConfigurator.java
src/java/org/apache/log4j/config PropertySetter.java
Log:
PropertySetter now extends ComponentBase. Modified PropertyConfigurator to
adapt to changes in PropertySetter.
Revis
On Jan 4, 2005, at 6:08 AM, Ceki Gülcü wrote:
At 08:53 PM 1/3/2005, Curt Arnold wrote:
In addition, it is probably not good to have "components" reference
the concrete LoggerRepository class. We should probably introduce an
interface (maybe "LoggerContext") that exposes the methods on
LoggerRe
ceki2005/01/04 07:09:55
Modified:src/java/org/apache/log4j/spi Filter.java ComponentBase.java
src/java/org/apache/log4j Layout.java Logger.java
Log:
Layout, Filter extend ComponentBase
Revision ChangesPath
1.9 +1 -16 logging-log4j/src/java/org
Updated http://www.qos.ch/logging/internalLogging.jsp with the new
guidelines.
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAI
ceki2005/01/04 04:51:20
Modified:src/java/org/apache/log4j/db ConnectionSource.java
DBAppender2.java ConnectionSourceSkeleton.java
src/java/org/apache/log4j/db/dialect Util.java
Log:
For methods in utility classes wishing to log the easiest
ceki2005/01/04 04:33:01
Modified:src/java/org/apache/log4j/db DBHelper.java
Log:
Removing superflous log statement as static utility classes should not log
without an explicit repository reference.
Revision ChangesPath
1.6 +2 -2 logging-log4j/src/java/org/
ceki2005/01/04 04:08:10
Modified:src/java/org/apache/log4j LogManager.java
Log:
Committing work in progress to allow at least correct compilation.
Revision ChangesPath
1.30 +10 -5 logging-log4j/src/java/org/apache/log4j/LogManager.java
Index: LogManager.
At 08:53 PM 1/3/2005, Curt Arnold wrote:
In addition, it is probably not good to have "components" reference the
concrete LoggerRepository class. We should probably introduce an
interface (maybe "LoggerContext") that exposes the methods on
LoggerRepository that "components" are expected to use.
At 07:39 PM 1/3/2005, Curt Arnold wrote:
On Jan 3, 2005, at 11:49 AM, Yoav Shapira wrote:
Hi,
I don't think it's a bad idea, but could there be a more specific or
domain-related name for it? Component(Base) is very generic, whereas
Appender(Skeleton) is more logging-domain-specific.
Yoav
--- Ceki
Component and ComponentBase are indeed generic names. However, these
classes are not for public consumption. They are intended to be used
*internally* by log4j components (Appenders, Layouts, Filters, Receivers,
ConnectionSources, etc.).
At 06:49 PM 1/3/2005, Yoav Shapira wrote:
Hi,
I don't thi
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project logging-log4j has an issue affecting its community integration.
This issue affect
31 matches
Mail list logo
