mwomack 2003/10/19 22:29:15
Modified:src/java/org/apache/log4j/plugins PluginSkeleton.java
PluginRegistry.java Plugin.java
Log:
Various cleanup.
Defined new method in Plugin, isEquivalent(). Used by PluginRegistry to see if 2
plugins are equivalent
mwomack 2003/10/19 22:27:15
Modified:src/java/org/apache/log4j/net XMLSocketReceiver.java
SocketReceiver.java SocketHubReceiver.java
JMSReceiver.java
Log:
Various cleanup.
Changed equals() method to new Plugin method isEquivalent
mwomack 2003/06/23 08:57:54
Modified:src/java/org/apache/log4j/plugins Receiver.java
Log:
Updated to implement new Thresholdable interface.
Removed comments about isActive. Want to review the whole "active" state.
Revision ChangesPath
1.4 +40 -8
mwomack 2003/06/23 08:56:31
Added: src/java/org/apache/log4j/spi Thresholdable.java
Log:
Added Thresholdable interface as suggested by Paul Smith with some modifications to
the methods signatures to better match similar/existing methods is AppenderSkeleton.
Revision Changes
mwomack 2003/06/10 23:37:45
Added: src/java/org/apache/log4j/plugins PluginRegistry.java
Log:
Added a new version of PluginRegistry that implements getPlugins methods.
Revision ChangesPath
1.1
jakarta-log4j-sandbox/src/java/org/apache/log4j/plugins
mwomack 2003/06/10 23:36:47
jakarta-log4j-sandbox/src/java/org/apache/log4j/plugins - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
mwomack 2003/06/10 22:57:50
Modified:.build.xml
Log:
Added helpers package to styled-files list.
Revision ChangesPath
1.9 +1 -0 jakarta-log4j-sandbox/build.xml
Index: build.xml
mwomack 2003/06/10 22:57:14
Modified:src/java/org/apache/log4j/helpers LoggerTraverse.java
Log:
Jalopy-ized, checkstyle'd version.
Revision ChangesPath
1.2 +119 -85
jakarta-log4j-sandbox/src/java/org/apache/log4j/helpers/LoggerTraverse.java
mwomack 2003/06/10 22:39:16
Added: src/java/org/apache/log4j/helpers LoggerTraverse.java
Log:
Added LoggerTraverse, a rough helper class that can be used to traverse Loggers in a
LoggerRepository and query their current level value.
Revision ChangesPath
1.1
mwomack 2003/06/10 22:38:15
jakarta-log4j-sandbox/src/java/org/apache/log4j/helpers - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
mwomack 2003/06/10 21:58:18
Added: src/java/org/apache/log4j/jdbc UrlConnectionSource.java
PreparedStatementSource.java
PreparedStatementParameter.java
PreparedStatementAppender.java
mwomack 2003/03/25 22:27:13
Modified:tests/src/java/org/apache/log4j/xml XMLLayoutTestCase.java
Log:
Test cases for testing output of MDC data, bug #18246, changes submitted by Paul
Smith.
Revision ChangesPath
1.6 +39 -0
jakarta-log4j/tests/src/java/org
mwomack 2003/03/25 22:27:03
Modified:tests/src/java/org/apache/log4j PatternLayoutTestCase.java
Log:
Test cases for testing output of MDC data, bug #18246, changes submitted by Paul
Smith.
Revision ChangesPath
1.6 +18 -0
jakarta-log4j/tests/src/java/org
mwomack 2003/03/25 22:26:48
Modified:tests/witness PatternParser_mdc
Added: tests/witness xmlLayout.mdc.2 xmlLayout.mdc.1
patternLayout.mdc.1
Log:
Test cases for testing output of MDC data, bug #18246, changes submitted by Paul
Smith.
Revision
mwomack 2003/03/25 22:26:33
Added: tests/input patternLayout.mdc.1.properties
Log:
Test cases for testing output of MDC data, bug #18246, changes submitted by Paul
Smith.
Revision ChangesPath
1.1 jakarta-log4j/tests/input/patternLayout.mdc.1
mwomack 2003/03/25 22:25:56
Modified:src/java/org/apache/log4j/xml XMLLayout.java log4j.dtd
Log:
Support for including MDC key/values in xml output, bug #18246, changes submitted by
Paul Smith.
Revision ChangesPath
1.20 +37 -0 jakarta-log4j/src/java/org/apache
mwomack 2003/03/25 22:24:56
Modified:src/java/org/apache/log4j/helpers PatternParser.java
Log:
Support for %X MDC option to print entire contents of MDC, bug #18246, changes
submitted by Paul Smith.
Revision ChangesPath
1.19 +23 -0
jakarta-log4j/src/java/org
mwomack 2003/03/25 22:23:57
Modified:src/java/org/apache/log4j PatternLayout.java
Log:
Support for %X MDC option to print entire contents of MDC, bug #18246, changes
submitted by Paul Smith.
Revision ChangesPath
1.19 +4 -2 jakarta-log4j/src/java/org/apache
I moved over the checkstyle 3.0 build changes into log4j-sandbox. The only
difference is that I turned on javadoc checking. We should turn this on in
the log4j cvs as well. I know it seems like busy work to fix all the
complaints, but it will be better in the long run.
-Mark
-
mwomack 2003/03/19 23:19:24
Modified:src/java/org/apache/log4j/servlet InitServlet.java
InitContextListener.java ConfigurationServlet.java
Log:
Jalopy-ized & checkstyled versions.
Revision ChangesPath
1.6 +2 -0
jakarta-log4j-san
mwomack 2003/03/19 23:18:32
Modified:src/java/org/apache/log4j/filter SetLocationInfoFilter.java
NDCMatchFilter.java MessageMatchFilter.java
MDCMatchFilter.java MatchFilterBase.java
LevelRangeMatchFilter.java
mwomack 2003/03/19 23:17:42
Added: src sun_checks.xml
Log:
Changes to use checkstyle 3.0.
Revision ChangesPath
1.1 jakarta-log4j-sandbox/src/sun_checks.xml
Index: sun_checks.xml
mwomack 2003/03/19 23:17:34
Modified:.build.xml
Log:
Changes to use checkstyle 3.0.
Revision ChangesPath
1.6 +13 -3 jakarta-log4j-sandbox/build.xml
Index: build.xml
===
RCS file
Hi all, I am replying to this email to the dev email list because I think it
is of general interest.
I spent some time recently evangelizing Scott to convert his Chainsaw
specific receiver code into the new general Receiver model, saying that he
could take the xml his UDPAppender was generating an
Richard, we haven't gotten Scott's cool stuff integrated yet, and we have
been changing things sufficiently to make it a challenge for Scott to
integrate. But hope is there.
Have you had a chance to look at the recent changes we have made to
Chainsaw? Not that the gui looks any different, but we
mwomack 2003/03/19 21:42:46
Modified:src/java/org/apache/log4j/chainsaw XMLFileHandler.java
MyTableModel.java EventDetails.java
DetailPanel.java ControlPanel.java
Log:
Changes to support display and filtering of property values
mwomack 2003/03/19 21:37:52
Modified:src/java/org/apache/log4j/spi LoggingEvent.java
Log:
Added getPropertyKeySet() method to return an unmodifiable set of the keys in the
event properties. If the properties is null, then an empty set is returned.
Revision ChangesPath
Paul,
> I've just started preparing for the change, and started off by thinking
> about the Test cases first.
>
> Am I correct in thinking that the following is the process to add a test
> case for log4j & MDC?:
>
> * modify XMLLayoutTestCase, add another test method for MDC.
> * create an xmlLayo
mwomack 2003/03/19 20:37:07
Modified:contribs/JayFunnell NetSendAppender.java
Log:
Submitting new version of NetSendAppender, per Jay Funnell. "The corrections were
provided by Volker Mentzner to handle the case where the native DLL is missing."
Revision Changes
mwomack 2003/03/18 23:03:35
Modified:src/java/org/apache/log4j/net SocketNode.java
JMSReceiver.java
Log:
Added code to set the property "log4j.remoteSourceInfo" in the event. For socket
related receivers, the value will be the remote host an
It is more than 40 words, but it might still help:
http://nagoya.apache.org/wiki/apachewiki.cgi?Log4JProjectPages/NDCvsMDC
-Mark
> -Original Message-
> From: Paul Smith [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 18, 2003 10:27 PM
> To: Log4j-Dev (E-mail)
> Subject: MDC & NDC & AC/D
mwomack 2003/03/18 22:04:11
Modified:src/java/org/apache/log4j/chainsaw XMLFileHandler.java
MyTableModel.java EventDetails.java
DetailPanel.java ControlPanel.java
Log:
Changes to display and filter the MDC values.
Revision
mwomack 2003/03/18 22:03:25
Modified:src/java/org/apache/log4j/chainsaw LoggingReceiver.java
Log:
Added deprecated javadoc info.
Revision ChangesPath
1.6 +2 -0
jakarta-log4j/src/java/org/apache/log4j/chainsaw/LoggingReceiver.java
Index
mwomack 2003/03/18 22:02:59
Modified:src/java/org/apache/log4j/spi LoggingEvent.java
Log:
Added getMDCKeySet() method to return an unmodifiable set of the keys in the MDC.
If the MDC is null, then an empty set is returned.
Revision ChangesPath
1.37 +22 -0
Inspired by some of the stuff Scott Deboy has been doing with his new
Chainsaw interface, I started looking to add the MDC to the DefaultViewer
(just applying some of the "apache way" and digging in to do it myself!). I
want to add a column that displays all the MDC key/value pairs in the
LoggingE
Hi Ceki,
I had a quick question about the recent addition of properties to
LoggingEvent. Why did you do this? Is is supposed to be something separate
from the MDC? I looks like each LoggingEvent has its own properties, so it
just seems like a duplication to me. I'm just trying to understand.
OK. It is checked into cvs.
Some future work:
- I would like to remove/change the static variables in ChainsawAppender.
Eventually multiple instances should be supported, each with their own
model.
- I would like to pass something different than the reference to the
ChainsawAppender to the activ
mwomack 2003/03/12 22:19:22
Modified:src/java/org/apache/log4j/chainsaw ChainsawAppender.java
Main.java Start.java
Added: src/java/org/apache/log4j/chainsaw ChainsawViewer.java
DefaultViewer.java
Log:
Changes to support generic
(psst...hey buddy, you wanna a Chainsaw viewer? I got one here cheap...)
:-)
> -Original Message-
> From: Oliver Burn [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 12, 2003 9:59 PM
> To: Log4J Developers List
> Subject: RE: Chainsaw patch - Create Main Window in ChainsawAppender
>
>
mwomack 2003/03/12 22:00:01
Modified:src/java/org/apache/log4j/chainsaw ChainsawAppender.java
Log:
Applied checkstyle changes from Paul Smith.
Revision ChangesPath
1.4 +84 -21
jakarta-log4j/src/java/org/apache/log4j/chainsaw/ChainsawAppender.java
Index
So, I have the changes to create instances of ChainsawViewer's from the
ChainsawAppender configuration. I moved the bulk of the code in Main into a
new class named DefaultViewer.
Would everyone prefer to see the changes as patches first or should I just
go ahead and check them into cvs? I'll ass
Here is a patch that moves the creation of the Main Chainsaw window from the
Start class to the ChainsawAppender class. It gets created in the
activateOptions() method of the ChainsawAppender class. I wanted to float
this patch before applying it in cvs.
- This is very much like the way LF5 work
> I've been working on the tab pane UI - which isn't released because it
> needs cleaned up and it includes the column sorting code provided by
> Claude Duguay and I haven't been told the T's have been crossed and the
> I's dotted.
Scott,
I guess your submission might hinge on this detail. I saw
> Perhaps the log4j community needs to formalise some sort of "feature
> requirements" for Chainsaw through discussion, and prioritise those on a
> release schedule basis. Once the requirements are ok-ed by the dev (and
> even the users themselves! :) ) community, then portions of everyone's
> res
Scott,
It sounds like you have been a very busy beaver. I think we are all
salivating at the prospect of seeing what you have done. A picture would
speak a thousand words, and actual jar files would speak volumes.
Regarding creating a new tool vs integrating with Chainsaw, it can go either
way.
mwomack 2003/03/10 20:24:50
Modified:.build.xml
Log:
Changes to use the Start class to executes Chainsaw instead of the Main class.
Revision ChangesPath
1.55 +2 -2 jakarta-log4j/build.xml
Index: build.xml
mwomack 2003/03/10 20:18:34
Modified:src/java/org/apache/log4j/chainsaw Start.java
Log:
Added a LocalDirectoryFinder to the FinderStrategies, after ResourceLoaderFinder,
but before FileOpenFinder. It looks for the config file in the current directory.
Revision Changes
mwomack 2003/03/08 18:42:07
Modified:.build.xml
Log:
Changes to include org.apache.log4j.plugins package in the log4j jar and javadoc.
Revision ChangesPath
1.53 +3 -1 jakarta-log4j/build.xml
Index: build.xml
> (1) I have some properties that are optional. I need to do some
> initialization of the appender based on these. I need to know when they
> are set and when all of the properties have been set. It would be great
> if there was a call that was made when the appender was ready to go...
> That wa
> Moving to the Jalopy tool is a great thing.
I almost forgot. Checkstyle too!
-Mark
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks to Marco Hunsicker, the author of Jalopy, I was able to work out the
header replacement/insertion issues. The "key" for the new and old header
has to be comprised of unique text contained in each. Given the correct
keys, Jalopy does a most excellent job of replacing the old header and not
mwomack 2003/02/27 21:10:59
Modified:src/jalopy log4j-coding-convention.xml
Log:
Updated version that removes old license header and inserts full Apache 1.1 License
header.
Revision ChangesPath
1.2 +14 -3 jakarta-log4j/src/jalopy/log4j-coding-convention.xml
mwomack 2003/02/27 21:10:13
Modified:src/java/org/apache/log4j/servlet InitServlet.java
InitContextListener.java CookieMDCFilter.java
ConfigurationServlet.java
Log:
Versions with full Apache License 1.1 header.
Revision Changes
mwomack 2003/02/27 21:09:29
Modified:src/java/org/apache/log4j/selector ContextJNDISelector.java
ContextClassLoaderSelector.java
Log:
Versions with full Apache License 1.1 header.
Revision ChangesPath
1.3 +47 -55
jakarta-log4j-sandbox
mwomack 2003/02/27 21:08:51
Modified:src/jalopy log4j-coding-convention.xml
Log:
Updated version that removes old license header and inserts full Apache 1.1 License
header.
Revision ChangesPath
1.2 +14 -3 jakarta-log4j-sandbox/src/jalopy/log4j-coding
Enclosed is an attempt to configure Jalopy to insert the fulle Apache 1.1
license at the top of the file. It inserts it at the top of the file, but
it does not remove the old header first. Plus, it seems to just keep
re-inserting the header everytime I run Jalopy. The Jalopy documentation
seems
> > The configuration for the event "sink":
> >
> >
> >
> >
> > http://jakarta.apache.org/log4j/";
> > debug="true">
> >
> >
> >
> >
> >
> >
> >
> > > value="%d{ABSOLUTE} %c: %m%n"/>
> >
> >
> >
> > > class="org.apache.log4j.net
Paul Smith wrote:
> > v1.3 is
> > going to have a
> > SocketReceiver (matching SocketAppender), SocketHubReceiver (matching
> > SocketHubAppender), JMSReceiver (matching JMSAppender), and
> > maybe more as
> > makes sense.
>
> That's very much what I was thinking, but I hadn't thought about the eve
Richard,
I don't entirely agree with your assessment. If you have a tool that is
working with current log4j, even if it only outputs property files, then
please submit it for the sandbox. It may drive some of the thinking and
convergence of the various logging packages.
-Mark
> -Original M
Paul Smith wrote:
> Another wacky concept might also be to have an option for a
> ChainSaw window
> to be able to define it's own Appender to write events being received to
> some other local Appender (sort of Daisy chain ChainSaw to forward to a
> local log4J system..) This way a remote server co
mwomack 2003/02/19 23:45:36
Modified:src/java/org/apache/log4j/servlet ConfigurationServlet.java
Log:
Jalopy-ized and checkstyle-d version.
Revision ChangesPath
1.2 +260 -234
jakarta-log4j-sandbox/src/java/org/apache/log4j/servlet/ConfigurationServlet.java
mwomack 2003/02/19 23:35:38
Modified:src/java/org/apache/log4j/servlet CookieMDCFilter.java
Log:
Jalopy-ized and checkstyle-d version.
Revision ChangesPath
1.2 +94 -77
jakarta-log4j-sandbox/src/java/org/apache/log4j/servlet/CookieMDCFilter.java
Index
mwomack 2003/02/19 23:32:51
Modified:.build.xml
Log:
Checked in property settings for checkstyle task. Allow "public" modifier in
interfaces. Allow protected members in classes.
Revision ChangesPath
1.5 +2 -7 jakarta-log4j-sandbox
mwomack 2003/02/19 23:18:32
Modified:src/java/org/apache/log4j/plugins Receiver.java
PluginSkeleton.java PluginRegistry.java Plugin.java
Log:
Jalopy-ized and checkstyle-d versions of the plugin files.
Revision ChangesPath
1.3 +24 -23
mwomack 2003/02/19 23:12:53
Modified:.build.xml
Log:
Checked in property settings for checkstyle task. Allow "public" modifier in
interfaces. Allow protected members in classes.
Revision ChangesPath
1.52 +2 -7 jakarta-log4j/build.xml
I propose that we place the current version of
o.a.log4j.jdbc.JDBCAppender.java into the log4j-sandbox (I don't know if we
should remove it altogether from the v1.3 release?). In doing so,
interested log4j developers need to step forward to begin the task of
continuing its development. I know Kev
mwomack 2003/02/18 21:51:47
Modified:.build.xml build.properties.sample
Removed: .sunCodingConvention.xml
Log:
Moved sunCodingConvention.xml to src/jalopy/log4j-coding-convention.xml and updated
build script accordingly.
Updated log4j-coding-convention to
mwomack 2003/02/18 21:50:54
Added: src/jalopy log4j-coding-convention.xml
Log:
Moved sunCodingConvention.xml to src/jalopy/log4j-coding-convention.xml and updated
build script accordingly.
Updated log4j-coding-convention to changes suggested by Jake (brought over version
from
mwomack 2003/02/18 21:49:34
jakarta-log4j/src/jalopy - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
mwomack 2003/02/18 21:43:17
Added: src/jalopy log4j-coding-convention.xml
Log:
Moved sunCodingConvention.xml to src/jalopy/log4j-coding-convention.xml and updated
build script accordingly.
Revision ChangesPath
1.1 jakarta-log4j-sandbox/src/jalopy
mwomack 2003/02/18 21:43:04
Modified:.build.xml build.properties.sample
Removed: .sunCodingConvention.xml
Log:
Moved sunCodingConvention.xml to src/jalopy/log4j-coding-convention.xml and updated
build script accordingly.
Revision ChangesPath
1.4
mwomack 2003/02/18 21:40:14
jakarta-log4j-sandbox/src/jalopy - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
#14827 fix is in place on 1.2 branch.
> -Original Message-
> From: Ceki Gülcü [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 18, 2003 10:24 AM
> To: Log4J Developers List
> Subject: RE: Possible 1.2.8 release
>
>
>
> Given that the existing JDBCAppender has other serious problems, I
mwomack 2003/02/18 21:21:42
Modified:src/java/org/apache/log4j/jdbc JDBCAppender.java
Log:
Fix for #14827.
Revision ChangesPath
1.8 +6 -0 jakarta-log4j/src/java/org/apache/log4j/jdbc/JDBCAppender.java
Index: JDBCAppender.java
mwomack 2003/02/18 21:04:49
Modified:docs Tag: v1_2-branch HISTORY
Log:
Mention of fix for #14827.
Revision ChangesPath
No revision
No revision
1.97.2.18 +5 -1 jakarta-log4j/docs/HISTORY
Index: HISTORY
mwomack 2003/02/18 20:55:57
Modified:src/java/org/apache/log4j/jdbc Tag: v1_2-branch
JDBCAppender.java
Log:
Fix for #14827, memory leak related to the "removes" buffer.
Revision ChangesPath
No revision
I did a quick review of open bugs. Besides the fix for #12366, I think we
should consider fixes for:
14827/16998 - JDBCAppender memory leak.
11570/16170 - Null Pointer Exception in XMLLayout.
I'll help with applying fixes if agreed.
-Mark
> -Original Message-
> From: [EMAIL PROTECTED]
Should we look through the open bugs and see if there are any others that we
should address for 1.2.8?
-Mark
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, February 15, 2003 6:21 AM
> To: [EMAIL PROTECTED]
> Subject: DO NOT REPLY [Bug 12366] -
Done. I changed "continuation" and "general" from 4 to 2. If there are any
other changes that should be applied, let me know.
-Mark
> -Original Message-
> From: Ceki Gulcu [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, February 15, 2003 7:38 AM
> To: [EMAIL PROTECTED]
> Subject: Indentati
mwomack 2003/02/15 11:13:39
Modified:.sunCodingConvention.xml
Log:
Changed indentation style from 4 to 2.
Revision ChangesPath
1.2 +2 -2 jakarta-log4j/sunCodingConvention.xml
Index: sunCodingConvention.xml
mwomack 2003/02/15 11:13:09
Modified:.sunCodingConvention.xml
Log:
Changed indentation style from 4 to 2.
Revision ChangesPath
1.2 +2 -2 jakarta-log4j-sandbox/sunCodingConvention.xml
Index: sunCodingConvention.xml
Yeah, maybe "core" is not the right word here. We need to distinguish
between what we are currently calling core (Logger, LoggerRepository,
filters, layouts, appenders, etc) and dependent supplemental tools like
Chainsaw, LF5, etc. Yes, they are part of log4j, but they are not needed to
use the "
> The commons-beanutils package is great. I use it all the time.
> Unfortunately, it depends on the commons-logging API which makes it
> unsuitable for use within log4j.
Ceki, I understand why this is true for the core log4j classes, but is this
also true for stand alone tools like this proposed
I put this together for the January Jakarta newsletter. If you have any
comments, please let me know. I figured I would give folks here a chance to
comment before sending it to Rob Oxspring for release.
-Mark
Log4j - a fast and flexible framework for logging application debugging
mes
All of Scott's suggestions are good. Ray, what are your interests in the
log4j code? What area would you like to look at/contribute to? We can
certainly suggest an area to look at, but if you have a specific area of
interest, then it will be more interesting, certainly. Your interest and
effort
mwomack 2003/02/07 23:55:35
Modified:.build.properties.sample build.xml
Added: .sunCodingConvention.xml
Log:
Moved over jalopy and checkstyle settings from jakarta-log4j cvs.
Revision ChangesPath
1.2 +4 -0 jakarta-log4j-sandbox
mwomack 2003/02/07 23:17:01
Added: src/java/org/apache/log4j/net SocketHubReceiver.java
Log:
Added SocketHubReceiver. As with SocketReceiver, test cases are forthcoming.
Revision ChangesPath
1.1
jakarta-log4j/src/java/org/apache/log4j/net
mwomack 2003/02/07 23:16:27
Modified:src/java/org/apache/log4j/net SocketNode.java
Added: src/java/org/apache/log4j/net SocketNodeEventListener.java
Log:
Added SocketNodeEventListener. This listener can be used by the SocketNode creator
to learn when the node closes the
mwomack 2003/02/07 22:57:50
Modified:src/java/org/apache/log4j/net SocketHubAppender.java
Log:
Cleanup of method declarations.
Revision ChangesPath
1.5 +19 -36
jakarta-log4j/src/java/org/apache/log4j/net/SocketHubAppender.java
Index: SocketHubAppender.java
Ceki,
> Whatever is in the sandbox cannot/should not be released at all! The
> point of the sandbox is to let developers unleash their talent without
> being limited by the committers. I think for example that Jacob should
> have write access to the log4j-sandbox so that he can continue working
>
Hi Richard,
> a) It would be nice to keep the core log4j package as small and
> efficient as possible.
Within reason.
> b) Allow sandbox classes to be built into independant jars (for
> instance, if all I need is core log4j and the smtp appender, then I'd
> deploye log4j.jar and log4j-smtp.jar w
Done. Thanks, Yoav!
My only comment is that whatever jalopy formats, our checkstyle target
should not complain about (except for javadoc non-compliance). So, we
should get the two in-sync. It would be primo is if checkstyle and jalopy
could use the same coding conventions xml file or descriptio
mwomack 2003/02/04 21:44:33
Modified:.build.xml
Log:
Fixed issue in compile.classpath definition.
Revision ChangesPath
1.47 +1 -1 jakarta-log4j/build.xml
Index: build.xml
===
RCS
mwomack 2003/02/04 21:42:21
Modified:.build.properties.sample build.xml
Added: .sunCodingConvention.xml
Log:
Changes to incorporate jalopy targets which can be used to format source code
(Thanks Yoav Shapira)
Added a "styled_files" file path
Done. Thanks, Luis!
I also added a target to build an executable jar for LF5. What if the user needs to
include an xml parser in the classpath for these jars?
-Mark
-Original Message-
From: Luis Reis [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 04, 2003 5:22 PM
To: Log4J
mwomack 2003/02/04 19:56:47
Modified:.build.xml
Log:
Added targets to build executable jars for chainsaw and lf5 gui viewers (thanks to
Luis Reis).
Modified core jar target to no longer include chainsaw and lf5 classes.
Revision ChangesPath
1.45 +66 -7
If someone wants to post an ant task that will do this, I will integrate
into the core build script.
-Mark
> -Original Message-
> From: Niclas Hedhman [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, December 12, 2002 9:31 PM
> To: Log4J Developers List
> Subject: Re: Log4J Log Viewer GUI (a
I checked in an updated checkstyle target, but the list of properties is not
complete. I am going to look at what some other projects have done. If
anyone has an opinion, now is the time.
-Mark
> -Original Message-
> From: Shapira, Yoav [mailto:[EMAIL PROTECTED]]
> Sent: Monday, Februar
I think we should discuss some options for the log4j-sandbox:
1) Are there any other items we want to move from the core log4j cvs into
the log4j-sandbox cvs? Classes from the varia package? Move the
contributor directories?
2) Should the log4j-sandbox packages be released independently of the
mwomack 2003/02/03 22:57:32
Added: tests/src/java/org/apache/log4j/filter
LevelMatchFilterTestCase.java
tests/witness filters.LevelMatchFilter.test1.txt
filters.LevelMatchFilter.test2.txt
1 - 100 of 246 matches
Mail list logo
