Hi,
I have a simple subclass of RollingFileAppender which works successfully
using log4j1.2.X but has never previously worked with 1.3 code.
Using the log4j1.3 alpha 8 code my custom subclass of the RFA wrapper now
compiles (after the replacement of direct property access with getter method
ac
Hi,
> -Original Message-
> From: Curt Arnold [mailto:[EMAIL PROTECTED]
> Sent: 28 October 2005 20:23
> To: Log4J Developers List
> Subject: Re: 1.2.13rc1 build
>
>
> On Oct 20, 2005, at 12:52 AM, Mark Womack wrote:
>
> I'm perplexed by the fix for TRACE level LocationInfo defect (Bug
> -Original Message-
> From: Curt Arnold [mailto:[EMAIL PROTECTED]
> Sent: 25 May 2005 23:59
> To: Log4J Developers List
> Subject: Re: Remove TRACE? Was: [VOTE] Modified Release Proposal
>
>
> What we need to make sure is that we have a reasonable incremental
> migration path from where
Hi,
> -Original Message-
> From: Scott Deboy [mailto:[EMAIL PROTECTED]
> Sent: 25 May 2005 18:45
> To: Log4J Developers List
> Subject: Remove TRACE? Was: [VOTE] Modified Release Proposal
>
> It seems odd to have one new feature as the only thing planned as the only
> thing that will eve
> -Original Message-
> From: Mark Womack [mailto:[EMAIL PROTECTED]
> Sent: 20 May 2005 18:17
> To: 'Log4J Developers List'
> Subject: RE: [VOTE][RESULT] Release Overview Proposal
>
> If there are problems or concerns about how it will affect the 1.2.X base,
> then yes, anyone can call a vo
Hi,
> -Original Message-
> From: Curt Arnold [mailto:[EMAIL PROTECTED]
> Sent: 13 May 2005 04:49
> To: Log4J Developers List
> Subject: Re: [VOTE] Release Overview
>
>
> On May 12, 2005, at 6:44 PM, Andy McBride wrote:
>
> > Hi,
> > The cur
Hi,
> -Original Message-
> From: Curt Arnold [mailto:[EMAIL PROTECTED]
> Sent: 12 May 2005 19:18
> To: Log4J Developers List
> Subject: Re: [VOTE] Release Overview
>
>
> On May 12, 2005, at 12:05 PM, Yoav Shapira wrote:
> >>> 3) Release a 1.4 version with the TRACE change and other fixes
Hi,
I also will be happy when I can replace my custom trace implementation with
built-in log4j functionality, but I dont think it should be done in the 1.2
branch.
The 1.2 branch effectively has a 'functionality freeze' on it which means
that I can upgrade individual apps to later versions of
Hi,
The log4j javadoc pagaes at:
http://logging.apache.org/log4j/docs/api/
are from the withdrawn 1.2.10 release which could cause some confusion for
new log4j users.
Just a 'heads-up'
Regards
Andy
-
To unsubscribe, e-m
Hi Curt,
> -Original Message-
> From: Curt Arnold [mailto:[EMAIL PROTECTED]
> Sent: 21 April 2005 02:31
> To: Log4J Developers List
> Subject: Re: SizeBasedRollingTest failing due to output/sizeBased-test2.1
> not existing
>
> Sorry to jump in so late. I'll try to review the assert's an
zeBasedTriggeringPolicy
implementation which uses this new API?
If not I will take a look at assessing the reliability and performance of
calling force().
Kind Regards
Andy
> -Original Message-
> From: Andy McBride [mailto:[EMAIL PROTECTED]
> Sent: 18 April 2005 2
> -Original Message-
> From: Andy McBride [mailto:[EMAIL PROTECTED]
> Sent: 18 April 2005 23:20
> To: Log4J Developers List
> Subject: SizeBasedRollingTest failing due to output/sizeBased-test2.1 not
> existing
>
> Hi,
>
> On a clean checkout of log4j he
Hi,
On a clean checkout of log4j head, the runAll target in tests/build.xml
fails on SizeBasedRollingTest due to output/sizeBased-test2.1 not existing.
Reverting the SizeBasedRollingTest class back to version 1.9 makes the test
succeed.
I'm running on ant 1.6.2 and jdk1.4.2 on WinXP.
Is t
Hi,
There appears to be a class missing from the log4j-1.2.9.jar in the current
distribution: org.apache.log4j.or.jms.MessageRenderer
This class was present in the 1.2.8 release but seems to have gone missing
since.
The source code for this class is still there and if I rebuild the
l
On Fri, 25 Feb 2005 22:22:19 +0100 Ceki Gülcü <[EMAIL PROTECTED]> wrote:
> I understand. OK, to summarize:
>
> 1) The changes are compile-time backward compatible -- existing appenders
> will compile just fine without change against 1.2 as well as 1.3.
>
> 2) The changes only affect programmatic c
As long as there is a 'core' log4j jar having only jdk 1.2
dependencies, any number of optional jars could be
produced to satisfy all deployment requirements.
e.g.
log4j.jar (core + ext = current API for compatibility)
log4j-core.jar (core classes)
log4j-ext.jar (all optional packages)
log4
Hi,
I would also prefer to have the default build target
either produce a full log4j.jar identical to the released
.jar or fail and produce nothing at all.
It would also be very useful, as Scott suggests, to have a
'build-nodeps' target which was capable of building a
minimal 'core' log4j.j
ugzilla I have to
> deal with now.
> >
> > But I'll support whatever this community wants. I
> understand that it
> > is
> > a distraction from log4j work (and frankly I don't have a
> lot of time
> > for that at the moment), but I think mov
fo.
All of this should be done really as a last resort -- the
servlet classes in
log4j should be (and I think are, so I'm wondering where
you see a need)
designed to the Servlet Specification...
Yoav
--- Andy McBride <[EMAIL PROTECTED]> wrote:
>
>Also, does anyone know if the
of bugzilla (preferably automatic by email) it would
be good.
Cheers
Andy
Yoav
--- Andy McBride <[EMAIL PROTECTED]> wrote:
Hi,
I used to get regular emails with a summary of open
log4j
bugs but I don't seem to have received one for quite a
while.
Has something changed with the bug
Also, does anyone know if there is a way to
programmatically detect the web
container the web app is running under? I am seeing a
need to have
different behavior between JBoss and Tomcat, and I was
just wondering if
there is a standard way to detect this.
-Mark
Mark,
The ServletContext has
Hi,
I used to get regular emails with a summary of open log4j
bugs but I don't seem to have received one for quite a
while.
Has something changed with the bugzilla config since the
move to logging.apache.org or is it just me not seeing
them?
It's a shame as it gave a good view of the qual
Hi,
I don't think the tests are using the 'old' package name for jetty - you
need to run jetty plus to get JNDI support.
The class: org.mortbay.jetty.plus.Server is located in the jar:
org.mortbay.jetty.plus.jar which is required in addition to
org.mortbay.jetty.jar
Regards
Andy
> -Orig
On Fri, 10 Dec 2004 16:26:55 +0100
Ceki Gülcü <[EMAIL PROTECTED]> wrote:
Yah, the JDBC 3.0 files are hard to find. I think they
are supposed to be shipped with the JDBC driver itself.
Consider making it explicit in the faq section 1.3 and the
build.properties.sample file that a jdbc3.0 provid
+1
This is even more important for a library like log4j than
an end-user app.
As an advocate of the KISS principle it has been an
education to see it put into practice by the log4j
committers.
IMHO a cautious attitude should be adopted towards all
feature changes at this stage.
New func
Hi,
Trying to build the current cvs head using jdk1.3 produces
the following errors:
With build.properties pointing to a valid
jdbc2_0-stdext.jar I get the following errors as the
methods used are from JDBC 3.0 which I can't seem to find
a jar for (other than using jdk1.4!)
jdbcExtension:
riven, but
we use the Embedded class above to run our own unit
tests, and I suspect it's
all we need for testing log4j as well.
This sounds good, thanks for the info.
Yoav Shapira http://www.yoavshapira.com
--- Andy McBride <[EMAIL PROTECTED]> wrote:
On Tue, 07 Dec 2004 20:21:48 +010
On Tue, 07 Dec 2004 20:21:48 +0100
Ceki Gülcü <[EMAIL PROTECTED]> wrote:
At 04:24 AM 12/4/2004, Andy McBride wrote:
Ok. The current frenzy around the 1.3 alpha release is
great to see. I would love
to help increase the quality of the release in any way I
can. I was hoping to find som
I raised bugzilla item 32536
(http://issues.apache.org/bugzilla/show_bug.cgi?id=32536)
for this issue and attached a patch and unit test
proposing a solution for this problem.
Cheers
Andy
On Mon, 06 Dec 2004 08:24:21 +1100
Paul Smith <[EMAIL PROTECTED]> wrote:
a) this is not bate
b) I'm not
Hi Jake,
On Sat, 04 Dec 2004 00:18:13 -0600
Jacob Kjome <[EMAIL PROTECTED]> wrote:
At 03:24 AM 12/4/2004 +, you wrote:
>Hi Ceki,
> I'm having several interesting problems
>trying to build and run the log4j unit tests at the
moment
>on my system which I suspect are due to my environment
not
Hi,
I have created a new thread: "Unit test dependencies"
to discuss this and other dependencies within the unit
tests.
On Wed, 01 Dec 2004 09:25:16 +0100
Ceki Gülcü <[EMAIL PROTECTED]> wrote:
Sorry about that.
It is really a peripheral. You could just copy NOPAction
to tests/. I don't min
Jacob Kjome <[EMAIL PROTECTED]> wrote:
At 03:24 AM 12/4/2004 +, you wrote:
>Hi Ceki,
> I'm having several interesting problems
>trying to build and run the log4j unit tests at the
moment
>on my system which I suspect are due to my environment
not
>being quite right yet after a recent clean O
.
I have also found this tool useful in the past, simply to
highlight areas of the code possibly in need of
love and attention.
Perhaps I should also create a bugzilla item to track this
NullPointer issue and link it to this thread so it
can be re-visited later with fresh-eyes when the current
spri
Please don't allow log4j to throw any unnecessary
RuntimeException's be they NullPointers or
IllegalStateExceptions.
According to the log4j FAQ question 1.2:
"log4j will not throw unexpected exceptions at run-time
potentially causing your application to crash. If for any
reason, log4j throws
ver classes follow the javadoc and provide redundant
implementations of both property and method whereas others just use the
inherited ones.
I suggest amendment of the javadoc in PluginSkeleton and removal of the
isActive() method and associated property in the following classes:
JMSReceiv
Hi,
As the Receiver performs the mirror function of the
Appender, would there be merit in striving to make the two
API's as similar as possible?
When writing an appender you have to implement the close()
method, but when writing a Receiver you have to implement
shutdown() but I believe the i
36 matches
Mail list logo
