Re: [EMAIL PROTECTED]: Project logging-log4j-tests (in module logging-log4j) failed

Hm. I think there is a bug in PropertyConfigurator where it does not output the configuration debug messages the second time. So, it is hard to see what is going on when it fails like this. I think there might be a problem in the reconfiguration around the file being copied while the configur

Re: svn commit: r391905 - in /logging/log4j/trunk: docs/ src/java/org/apache/log4j/ src/java/org/apache/log4j/joran/ src/java/org/apache/log4j/spi/ src/java/org/apache/log4j/watchdog/ src/java/org/apa

Using an InputStream is a problem since it would cause any XML configuration that contained external entities to fail to parse. For example, if you have a document like: ]> &stdAppenders; ... This document would successfully parse when DOMConfigurator.configurator(File) is call

Re: svn commit: r391905 - in /logging/log4j/trunk: docs/ src/java/org/apache/log4j/ src/java/org/apache/log4j/joran/ src/java/org/apache/log4j/spi/ src/java/org/apache/log4j/watchdog/ src/java/org/apa

I checked in a bunch of changes. Hopefully it isn't more broken than before. The tests for FileWatchdog are just too intricate. The config file could be getting read by watchdog, so can't be deleted as required in the tests, so I had to add some code to loop on deleting. Then it seems that i

Re: Compile error

commit it to the 1_2-branch after lunch. On Apr 5, 2006, at 12:27 AM, Mark Womack wrote: I am getting these compile errors when compiling with 1.3. The getOffset(long) method is not supported in jdk 1.3: [javac] F:\development\code-svn-apache-projects\logging-log4j \tests\src\java\org\

1.3 build

Hi all, I obviously haven't done the next build for v1.3. I am trying to get some changes together for the FileWatchdog. I am just rewriting it to be much simpler. I have the changes ready to go, so after we fix the current compile errors I will test and check in. I also think we should r

Compile error

I am getting these compile errors when compiling with 1.3. The getOffset(long) method is not supported in jdk 1.3: [javac] F:\development\code-svn-apache-projects\logging-log4j\tests\src\java\org\apache\log4j\helpers\DateLayoutTest .java:239: cannot resolve symbol [javac] symbol : meth

Fw: Log4j 1.2.13

Forwarding to the log4j dev mailing list. -Mark - Original Message - From: "Janet Campbell" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, March 16, 2006 11:47 AM Subject: Log4j 1.2.13 Hi there, In reviewing this version of Log4j for inclusion in Eclipse, I found ref

Re: [EMAIL PROTECTED]: Project logging-log4j-tests (in module logging-log4j) failed

The complete output for this test is below. At first blush, it appears that the second config file is not parsed correctly, so the level is never changed to INFO, so the test eventually times out waiting for the change. Not sure why the file is failing in some cases. Will probably need to turn

Re: [EMAIL PROTECTED]: Project logging-log4j-tests (in module logging-log4j) failed

Any idea why these failures are happening? The CoreTestSuite class looks like it should execute its tests as before...I don't have access to my home machine right now, otherwise I would run all the tests to check it. -Mark On 3/12/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > To whom it may

Re: Log4j wiki under attack?

I deleted the recently added pages. We'll see where it goes from there. thanks, Ceki. -Mark - Original Message - From: "Ceki Gülcü" <[EMAIL PROTECTED]> To: "Log4J Developers List" Sent: Thursday, March 02, 2006 11:07 AM Subject: Log4j wiki under attack? Hello all, I am not 100% s

Re: 1.3-alpha-9 build

hoo! -Mark On 3/2/06, Curt Arnold <[EMAIL PROTECTED]> wrote: > > On Mar 2, 2006, at 1:02 AM, Mark Womack wrote: > > > I will be doing the build tomorrow night (3/2). If you have any > > checkins or updates to the HISTORY.txt, please get them in before > > 6pm US P

Re: [EMAIL PROTECTED]: Project logging-log4j (in module logging-log4j) failed

This must be because of my build.xml changes around version. But where in the gump specs does it say that the build variable "version" will be replaced by @@DATE@@? I changed the variable used in all the jar names from version to fullVersion, so I am guessing this is the issue. I can change i

1.3-alpha-9 build

I will be doing the build tomorrow night (3/2). If you have any checkins or updates to the HISTORY.txt, please get them in before 6pm US Pacific time. thanks, -Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additiona

Re: [POLL] Base JDK version support for log4j 1.3?

I mentioned the Scheduler specifically, but we can start using more of the "recent" standard jdk classes. I think that is a plus. And we are focusing on backwards compatibility with our own api. -Mark On 2/23/06, Yoav Shapira <[EMAIL PROTECTED]> wrote: > Hola, > Since 1.3 is so focused on backw

Re: [POLL] Base JDK version support for log4j 1.3?

Part of the equation is also the web application servers like JBoss, etc. They are all on 1.5/5 now, but they weren't for a while there. -Mark On 2/23/06, Jess Holle <[EMAIL PROTECTED]> wrote: > The real question is how many people will not upgrade to the latest > stable JVM yet want to upgrade

[POLL] Base JDK version support for log4j 1.3?

We have talked about this before, and I plan to poll the user list, but I thought we could talk about it some more here first. What base JDK version do we want to support for log4j 1.3? > JDK 1.2? > JDK 1.3? Cons: - not as universal of an option for logging Pros: - can use more modern, builtin

Re: Next 1.3alpha build

good, any luck tracking down that intermittent test case issue? > > Paul > On 23/02/2006, at 10:40 AM, Mark Womack wrote: > > > Unless there are objections, I am going to plan in doing the next 1.3 > > alpha build next Wednsday (3/1) instead of tonight. I know there are > &

Next 1.3alpha build

Unless there are objections, I am going to plan in doing the next 1.3 alpha build next Wednsday (3/1) instead of tonight. I know there are some things I want to get in before that. speak up if you'd rather see the build today, thanks, -mark ---

Re: Encryption Question

No version of log4j provides any explicit encryption support. -Mark On 2/21/06, Joan Drejer <[EMAIL PROTECTED]> wrote: > Ceki Gülcü qos.ch> writes: > > > > > > > You mean encrypted license protection or do you mean encrypted output? The > > answer to both questions is no. HTH, Ceki > > > > At 12

Re: How to print request headers and sessin attributes log4j logging

See the documentation for the MDC class. You will need to do some setup via a servlet Filter or other mechanism, and it will only apply to the thread handling the request. hth, -Mark On 2/18/06, sreenivas velagapudi <[EMAIL PROTECTED]> wrote: > Hi, > Is there any way i can print the request

Re: [logging] JCL2.0 design - Architecture

Hi Boris, It is a bit early for us to put any real details around log4j 2.0. I think it is going to be some fundamental rethinking of the api, etc. So, to say that log4j 2.0 will provide a native implementation of o.a.c.l.Log, I am not sure. Maybe other committers have an opinion. I suspect th

Re: [EMAIL PROTECTED]: Project logging-log4j-tests (in module logging-log4j) failed

Does anyone know how to get access to the output files for this gump run? -Mark On 2/20/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > 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,

Re: About NDC/MDC and threads

Raul, It's been a while since I have looked at this, and while it is possible, there is no built in support in log4j to do what you want. Mainly because there is no standard way to get at an HttpSession across web servers, akaik. And if there was, or you wrote some customized code, how would you

Re: [EMAIL PROTECTED]: Project logging-log4j-tests (in module logging-log4j) failed

Well, it likes it is being consistent. I will be checking in some better instrumented code tonight to see if I can start tracking this down better. -Mark On 2/13/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > To whom it may engage... > > This is an automated request, but not an unsolicited o

log4j 1.3 alpha 8 release now available

The log4j team is happy to announce the availability of log4j version 1.3alpha8. It can be downloaded from: http://logging.apache.org/site/binindex.cgi This version contains many changes to bring it back to better compatibility with log4j version 1.2.X, and more changes are planned for the up

log4j 1.3 alpha 8 status

The PMC approved the release, so I will be working on getting it on the dist tomorrow evening. Once it is out there, I will send an announcment to log4j-user. thanks, -Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For

Re: Individual contributor licence agreement

Yep. Thanks, Curt. So, we had talked about putting Elias' new stuff in the sandbox. Are we still good with that as a start? -Mark On 2/6/06, Curt Arnold <[EMAIL PROTECTED]> wrote: > > On Feb 6, 2006, at 12:12 PM, Mark Womack wrote: > > > Elias, > > >

Re: Individual contributor licence agreement

Elias, Sometimes the feedback about the submitted license is not great, but if you faxed it in, I'm sure Jim (ASF Secretary) has processed it. There is a page where one can see if the license has been received. I can't seem to find the web link to it, but it I can look it up in a svn repo when I

Re: [VOTE] Release log4j 1.3alpha8

es or release as is (since they are intermittent). You can monitor general@ yourself or I will let folks know the status later today. -Mark On 2/1/06, Mark Womack <[EMAIL PROTECTED]> wrote: > > In this case, I would suggest: > > > > 1. Copy the contents of log4j/trunk to log4j/

Re: [COMPATIBILITY] Current state

just wanted to receive levelChangedEvent() calls when possible > >> (so I can fire JMX notifications on this basis). > >> > >> Overall 1.3 alpha 8 worked just fine from my short testing. Good > >> work everyone! > >> > >> -- > >> Jes

Re: [VOTE] Release log4j 1.3alpha8

In this case, I would suggest: 1. Copy the contents of log4j/trunk to log4j/tags/v1.3alpha8 2. Update the contents of log4j/trunk/src/xdocs/download.xml and other files to reflect pending release of log4j 1.3alpha8 3. Announce the results of the vote 4. Prepare signatures for the tarball and z

Re: [VOTE] Release log4j 1.3alpha8

So, I assume I can copy out the /trunk up one level and then delete /trunk. That should fix this tag mess. -Mark On 2/1/06, Curt Arnold <[EMAIL PROTECTED]> wrote: > > On Feb 1, 2006, at 2:37 PM, Mark Womack wrote: > > > >> > >> I did not see a SVN commit

Re: [VOTE] Release log4j 1.3alpha8

On 2/1/06, Curt Arnold <[EMAIL PROTECTED]> wrote: > > On Feb 1, 2006, at 11:04 AM, Mark Womack wrote: > > > I'm pretty sure that I did not update to the latest site contents > > before doing the a8 build. Oversight on my part. If that makes a > > concrete d

Re: [VOTE] Release log4j 1.3alpha8

lease (updating download.xml, other 1.3a8 info, etc). > > -Mark > > On 1/31/06, Curt Arnold <[EMAIL PROTECTED]> wrote: > > > > On Jan 31, 2006, at 3:16 PM, Mark Womack wrote: > > > > > http://cvs.apache.org/builds/logging/log4j/log4j-1.3a8 > >

Re: [VOTE] Release log4j 1.3alpha8

<[EMAIL PROTECTED]> wrote: > > On Jan 31, 2006, at 3:16 PM, Mark Womack wrote: > > > http://cvs.apache.org/builds/logging/log4j/log4j-1.3a8 > > > > I'd like to move on this. I won't be available Thursday or Friday to > > push the release to dist. >

[VOTE] Release log4j 1.3alpha8

http://cvs.apache.org/builds/logging/log4j/log4j-1.3a8 I'd like to move on this. I won't be available Thursday or Friday to push the release to dist. +1 -Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands

log4j 1.3 alpha 8 redux

http://cvs.apache.org/builds/logging/log4j/log4j-1.3a8 - Built with JDK 1.3. - Built with Ant 1.6.5. - Built using the MinGW 3.1.0-1 for the NTEventAppender.dll. - Passes all tests (I had to add the xml related jars to the test classpath for them to run under jdk 1.3). - Replaced the jars alrea

Re: log4j 1.3alpha8 build

i definitely had the wrong binary for mingw. i'll post status later this evening. -Mark On 1/30/06, Curt Arnold <[EMAIL PROTECTED]> wrote: > > On Jan 30, 2006, at 2:02 PM, Mark Womack wrote: > > > Of the 4 items mentioned, the jdk 1.3/1.4 issue is the biggest. But

Re: log4j 1.3alpha8 build

Of the 4 items mentioned, the jdk 1.3/1.4 issue is the biggest. But it looks like the 1.4 dependencies have been resolved? If so, then I can rebuild using 1.3, remove the breakiterator, and upgrade to Ant 1.6.5. None of those will be hard to setup. I need to look at the .dll build issue. I sus

log4j 1.3alpha8 build

http://cvs.apache.org/builds/logging/log4j/log4j-1.3a8/ Take a look at it. I plan to generate the compatibility report and post it someplace. I still need to figure out the problem with my building the dll. -Mark - To u

1.3alpha-8 build in progress

I've started on the build. I had to remove the building of the nt dll. I don't have the right stuff or something and don't want to delay anymore. I'll figure it out before the alpha-9 build. I left the targets in place so people can build locally if they want. It also looks like the api doc

1.3 alpha 8 build

I have spent the evening getting everything setup from scratch to do a clean build and I still have some issues with the mingw setup. I will be resolving them tomorrow evening. So the checkin deadline is extended until 7pm tomorrow. If anyone has updates for the HISTORY.txt file, now would b

Re: svn commit: r370726 - in /logging/log4j/trunk/tests/witness/watchdog: watchdog.FileWatchdog.test1.txt watchdog.FileWatchdog.test2.txt

actual documentation, not just an external link. But then, documentation in general needs work, as noted before. (glad to see you are still out there, Ceki!) -Mark On 1/25/06, Ceki Gülcü <[EMAIL PROTECTED]> wrote: > At 05:46 AM 1/25/2006, Mark Womack wrote: > > >>Do we wa

Re: Upcoming log4j 1.3 alpha 8 build

Curt, what do I need to install to run the compatibility report? Last time I looked, I needed some special version of BCEL(?) that I could not find... -Mark On 1/25/06, Yoav Shapira <[EMAIL PROTECTED]> wrote: > Hi, > > >Should we include the latest compatibility report? > > That would be a nice

Re: [COMPATIBILITY] Current state

Jesse, we'll be very interested in what you find compatibility-wise with the new alpha-8 version. :-) -Mark - Original Message - From: "Jess Holle" <[EMAIL PROTECTED]> To: "Log4J Developers List" Sent: Tuesday, January 24, 2006 11:05 AM Subject: Re: [COMPATIBILITY] Current state

Re: svn commit: r370726 - in /logging/log4j/trunk/tests/witness/watchdog: watchdog.FileWatchdog.test1.txt watchdog.FileWatchdog.test2.txt

On Jan 24, 2006, at 10:02 PM, Mark Womack wrote: Curt, before I re-enable the FileWatchdog test case, can you try it on your machine? I cleaned it up some, but looking at the code I'm not sure how it was still printing the debug message. It explicitly checks the level on the logg

Re: svn commit: r370726 - in /logging/log4j/trunk/tests/witness/watchdog: watchdog.FileWatchdog.test1.txt watchdog.FileWatchdog.test2.txt

Curt, before I re-enable the FileWatchdog test case, can you try it on your machine? I cleaned it up some, but looking at the code I'm not sure how it was still printing the debug message. It explicitly checks the level on the logger is INFO before printing any messages. But try it now. tha

Upcoming log4j 1.3 alpha 8 build

I am still planning to do the next 1.3 build (alpha 8) tomorrow evening. If you have any changes you want to make it in, please have them checked into svn by 7pm US pacific time. I think we need to update some documentation about the 1.3 version to reflect the work we are doing to have 1.2 ap

Re: svn commit: r370726 - in /logging/log4j/trunk/tests/witness/watchdog: watchdog.FileWatchdog.test1.txt watchdog.FileWatchdog.test2.txt

That could be. I did tighten up the times. I'll change the times and add the test back in. -Mark - Original Message - From: "Curt Arnold" <[EMAIL PROTECTED]> To: "Log4J Developers List" Sent: Thursday, January 19, 2006 8:46 PM Subject: Re: svn commit: r370726 - in /logging/log4j/

TimeBasedRolling unit test fails (sometimes)

I haven't had a chance to look at this, but it has happened to me twice at various times. Sometimes the TimeBasedRolling unit test fails. Most of the time it is fine, but sometimes there is a missing file: TimeBasedRolling: [junit] Running org.apache.log4j.rolling.TimeBasedRollingTest [

Re: [EMAIL PROTECTED]: Project logging-log4j-tests (in module logging-log4j) failed

I'll fix it this evening. The test is correct, the witness file is bad. I swear I checked these witness files before checking them in. This was the base I needed to create the tests for the configureAndWatch() methods for DOMConfigurator and PropertyConfigurator. I'll see if I can get those che

Re: Contribution of non-blocking socket appender

1) You need to file a signed CLA with the ASF. See this link under "Contributor License Agreements" for details: http://www.apache.org/licenses/ 2) Submit code via a bug report. All source files must have the proper ASF license header. You can find an example of this in the current code. 3) I

Re: log4j 1.3 prioritized tasks

Curt is right. Submitting a CLA and resubmitting the code with proper ASF headers, etc should be sufficient. See this link, under "Contributor License Agreements": http://www.apache.org/licenses/ My question before was if you were suggesting a different set of "fine grain" classes that co-exist

Re: [EMAIL PROTECTED]: Project logging-log4j-tests (in module logging-log4j) failed

hursday, January 05, 2006 12:18 PM Subject: Re: [EMAIL PROTECTED]: Project logging-log4j-tests (in module logging-log4j) failed On Jan 5, 2006, at 11:47 AM, Mark Womack wrote: I'll take a look at this tonight if no one gets a chance before then. Not sure what is up, but might be related t

Re: [EMAIL PROTECTED]: Project logging-log4j-tests (in module logging-log4j) failed

I'll take a look at this tonight if no one gets a chance before then. Not sure what is up, but might be related to my recent build changes? I did not get this error when I ran the tests with my build changes, so it has me a bit confused. -Mark On 1/5/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wr

Re: [EMAIL PROTECTED]: Project logging-log4j (in module logging-log4j) failed

Thanks. I will fix it this evening. -Mark On 1/3/06, Curt Arnold <[EMAIL PROTECTED]> wrote: > > On Jan 3, 2006, at 11:20 AM, Mark Womack wrote: > > > This is because of the build changes I just made. For those that have > > experience with this, how do I update gu

Re: [COMPATIBILITY] DOMConfigurator

to the new code will be provided. -Mark On 1/3/06, Endre Stølsvik <[EMAIL PROTECTED]> wrote: > On Mon, 2 Jan 2006, Mark Womack wrote: > > | I was looking at this class in regards to compatibility with 1.2. I was > | interested in restoring the configureAndWatch methods. > &g

Re: [EMAIL PROTECTED]: Project logging-log4j (in module logging-log4j) failed

This is because of the build changes I just made. For those that have experience with this, how do I update gump so that it knows the new location for the jar? -Mark On 1/3/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > To whom it may engage... > > This is an automated request, but not an un

[COMPATIBILITY] LoggerRepository & LoggerRepositoryEx

I see that we moved the methods that had been added to LoggerRepository for 1.3 into LoggerRepositoryEx. My question is why? Is it very likely that any users of log4j have implemented their own instance of LoggerRepository and not used the version implemented in Hierarchy? Where would they e

Re: [COMPATIBILITY] DOMConfigurator

Yeah, the configureAndWatch methods would be added back for PropertyConfigurator too. OK, I'll add those back in tomorrow. Coming up with the test cases will take the time. And we should start a document of the "expected differences" and pass that on the user list with each release. -Mark

Concurrency (was Re: log4j 1.3 prioritized tasks)

Elias, you are proposing that there be a new/different set of "concurrent" appenders? One that do not suffer from the problem that has been identified? -Mark - Original Message - From: "Elias Ross" <[EMAIL PROTECTED]> To: "Log4J Developers List" Cc: "Curt Arnold" <[EMAIL PROTECTED]

[COMPATIBILITY] DOMConfigurator

I was looking at this class in regards to compatibility with 1.2. I was interested in restoring the configureAndWatch methods. This should be easy to do and just have them use the new Plugin code to provide the same functionality, but better because now the watchers can be shutdown properly o

Re: log4j 1.3 prioritized tasks

I think that achieving as much binary compatibility with 1.2.X as possible should be a big goal for 1.3 (I know I keep saying it). Easing a transition to some of the bigger features/additions will be better for the community. However, if there are changes that we feel are important enough, but

1.3 builds

Going forward I plan to do 1.3 alpha builds on the last Wednesday of every month. Whatever is there gets included. We can do more builds if warranted, but I think that for the alpha time period, this will be sufficient. The next 1.3 alpha build will be on 1/25, and it will be alpha 8. I th

Re: SyslogAppender and compatibility report

t;[EMAIL PROTECTED]> wrote: > > On Dec 21, 2005, at 8:06 PM, Mark Womack wrote: > > > Curt, > > > > I'm confused by some of the items in the report. For example, there > > is this one: > > > > o.a.l.net.SocketHubAppender Class > > org.apache

Re: log4j 1.3 prioritized tasks

I was pretty tired last night, so maybe my reaction as "shameful" was a little much. But I still believe there is a lot of room for improvement that needs to be done. If you look at the documentation we have, there is the short introduction (which is old and needs some updating; it doesn't even t

Re: log4j 1.3 prioritized tasks

http://wiki.apache.org/logging-log4j/Log4j13PrioritizedTasks - Original Message - From: "Yoav Shapira" <[EMAIL PROTECTED]> To: "Log4J Developers List" Sent: Wednesday, December 21, 2005 6:29 PM Subject: Re: log4j 1.3 prioritized tasks Perhaps this prioritized list belongs on a wiki p

Re: log4j 1.3 prioritized tasks

Well, one can argue that build changes should be deprioritized. I'm the one that is using it to do the official builds and releases, so I might have a biased view. But I don't agree with the documentation. We REALLY need to do something. I think our current state is pretty shameful. I'd lik

log4j 1.3 prioritized tasks

I prioritized the task list from the previous thread. Not all of these are dependent on each other, but I beleive that we should look at completing the first 2 before seriously tackling anything else. The last 4 could happen in any order and most likely in parallel. Documentation will get setup

Re: 1.3 Tasks (and beyond)

Yes. log4j 2.0 would need to be in a new package. But hopefully the client upgrade might be as simple as changing the package imports. Now extensions or more complicated configuration would probably need to be rewritten. -Mark On 12/20/05, Jess Holle <[EMAIL PROTECTED]> wrote: > Ma

Re: SyslogAppender and compatibility report

Curt, I'm confused by some of the items in the report. For example, there is this one: o.a.l.net.SocketHubAppender Class org.apache.log4j.net.SocketHubAppender removed but when I look at the head, o.a.l.net.SocketHubAppender is there. So, why does the report say it was removed? -Mark >

Re: 1.3 Tasks (and beyond)

Comments below. On 12/19/05, Scott Deboy <[EMAIL PROTECTED]> wrote: > There are other issues we need to resolve as well, including: > - do we really want one jar for each external dependency (oro, xml, etc.) > - there are two expression language implementations I'll add these to my master list.

1.3 Tasks (and beyond)

As Curt has mentioned, we got together for a little while to talk about 1.3 stuff. I have included the list of tasks we came up between ourselves. I'm sure it is not complete, but gives an idea of some scope. Please feel free to comment and add more as you see it. The one thing that really

Re: Exploration of use of Maven for site generation and build

Yeah, we are talking Maven2 here. It appears to be a really big improvement over Maven1. -Mark - Original Message - From: "Scott Heaberlin" <[EMAIL PROTECTED]> To: "Log4J Developers List" Sent: Sunday, December 18, 2005 8:01 AM Subject: Re: Exploration of use of Maven for site gener

Re: Exploration of use of Maven for site generation and build

I think, but need to prove, that a Maven2 build will be easier than the Ant version. I agree that getting 1.3 out the door is a higher priority, but updating our documentation is a pretty high item for 1.3 (IMO) and if Maven2 makes this better/easier, then I am willing to make it happen. -Ma

Re: Exploration of use of Maven for site generation and build

, IMHO. -Mark - Original Message - From: "Ceki Gülcü" <[EMAIL PROTECTED]> To: Sent: Monday, December 19, 2005 8:02 AM Subject: Re: Exploration of use of Maven for site generation and build At 12:07 AM 12/17/2005, Curt Arnold wrote: Mark Womack, Ron Grabowski (from log4ne

1.2.13 is released...

...and available for download. I updated the site, etc as you have seen from all the commit messages. (Travelling for ApacheCon tomorrow. Looking forward to it.) -Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For addi

[Release update] was: [Bug 9606] - NTEventLogAppender.dll missing in .zip file

agree. -Mark - Original Message - From: "Curt Arnold" <[EMAIL PROTECTED]> To: "Log4J Developers List" Sent: Wednesday, December 07, 2005 12:26 PM Subject: Re: DO NOT REPLY [Bug 9606] - NTEventLogAppender.dll missing in .zip file On Dec 6, 2005, at 10:25 PM, Ma

Re: DO NOT REPLY [Bug 9606] - NTEventLogAppender.dll missing in .zip file

Erg. The dll is not checked into svn (or the old cvs repository either). Or am I missing it? It is not under src/java/org/apache/log4j/nt. Didn't we make a conscious decision to remove the .dll from the distribution/repository? Folks are supposed to build it for themselves for some reason?

1.2.13 Official Build

http://cvs.apache.org/builds/logging/log4j/log4j-1.2.13 I tagged both the log4j v1_2-branch and the logging-site trunk. I have not made any of changes to the logging site svn to reflect the 1.2.13 download, pending official release vote from the PMC. I will sign the binaries and update the s

Re: Log4j 1.3 Woes

On 11/29/05, Jess Holle <[EMAIL PROTECTED]> wrote: > I appreciate the forthright responses from you, Curt, and others. No reason for anything else from anyone here. We all want to do the right thing. > I apologize for getting a bit hot on these issues. It would be good if > the 1.3 documentati

[RESULT][VOTE] Release of log4j 1.2.13

This proposal has been accepted by the log4j committers, with positive votes from the community at large.  I will do the official tagging and building this Saturday (I'll be sure to tag the site as well). -Mark

[VOTE] Release of log4j 1.2.13

This is a vote to release the 1.2.13rc2 as the official release for 1.2.13. If accepted by the committers and the PMC, then I will build the official version from the current 1.2 branch head. +1 -Mark - To unsubscribe, e

Re: Log4j 1.3 Woes

Jess, There are more class/source/binary incompatibilities in the 1.3 alpha version of log4j than most people are happy with. You are not the first to outline them. Curt Arnold has also detailed a number that he was concerned about. It is an item that will be addressed as we march to beta.

1.2.13rc2 Build

- used latest ConsoleAppender changes with "follow" instead of "honorReassignment". - updated HISTORY.txt - updated build.xml to 1.2.13rc2 - Created a v1_2_13_rc2 tag in svn Build can be accessed from: http://cvs.apache.org/builds/logging/log4j/log4j-1.2.13rc12/ -Mark -

Re: [Chainsaw]: Placing Jars in the SVN repo

We should check on the BSD and JmDNS licenses.   But I am all for it in concept. Isn't there a [EMAIL PROTECTED] where we can ask the license question? -MarkOn 11/14/05, Paul Smith <[EMAIL PROTECTED]> wrote: Anyone have any objection to putting some ASL licensed jars in theChainsaw repo? Rather t

Re: [VOTE] Release of log4j 1.2.13

;be changed to "follow". >Yes, what's the rush?  At least get it right.  I won't block, but might as well let Curt make the change before release.+0Jake > >On Nov 6, 2005, at 10:20 PM, Mark Womack wrote: > >> This is a vote to release the 1.2.13rc1 as the offic

[VOTE] Release of log4j 1.2.13

This is a vote to release the 1.2.13rc1 as the official release for 1.2.13. If accepted by the committers and the PMC, then I will build the official version from the current 1.2 branch head. +1 -Mark - To unsubscribe, e

Re: JBoss and deadlock issues

whatever reasons. I would much rather get on with 1.3 and do it the right way there.  -MarkOn 11/4/05, Endre Stølsvik <[EMAIL PROTECTED]> wrote: On Thu, 3 Nov 2005, Mark Womack wrote:| The wrapper class would only be in 1.2 and really only used to avoid making| everyone take the "big&quo

Re: JBoss and deadlock issues

s for the class being wrapped"... How does the configuration of the 'wrapped' class get configured?PaulOn 04/11/2005, at 1:09 PM, Mark Womack wrote:OK, stop me if this sounds completely crazy.  It might. What if we created a wrapper class for subclasses of AppenderSkeleton

Re: JBoss and deadlock issues

code, but thought I would bounce it out there. -MarkOn 11/3/05, Mark Womack <[EMAIL PROTECTED]> wrote: Yes, it is on the "list" for 1.3. The last message in the thread is from 10/21.  Do you have any update since then?  I really hate leaving this hanging in 1.2.  I would like to

Re: JBoss and deadlock issues

Yes, it is on the "list" for 1.3. The last message in the thread is from 10/21.  Do you have any update since then?  I really hate leaving this hanging in 1.2.  I would like to find a solution that does not break subclasses of AppenderSkeleton.  Don't know what that would be yet. -MarkOn 10/31/05

Re: [VOTE] log4j 1.3 alpha 7 release

think we need a vote to release an alpha (or beta, +or RC)build, only a vote on declaring something stable.Yoav--- Jacob Kjome <[EMAIL PROTECTED]> wrote:> Quoting Mark Womack < [EMAIL PROTECTED]>:>> > This is vote to decide if the current build of log4j 1.3 alpha 7>

[RESULT] [VOTE] log4j 1.3 alpha 7 release

Just for some finality, the release of this alpha version was approved.  I will be moving it to the download areas tonight, signed, etc. thanks, -Mark

Re: [PATCH] SyslogAppender leaks sockets

Ian, can you please submit this patch as a bug report?  That way we won't lose track of it. And thanks for the submission! -MarkOn 10/26/05, Ian Reilly <[EMAIL PROTECTED]> wrote: The attached patch for version 1.2.12 fixes two problems in org.apache.log4j.net.SyslogAppender.  First, it doesn't c

Re: [VOTE] log4j 1.3 alpha 7 release

apira <[EMAIL PROTECTED]> wrote: Hi,+1, and I also don't think we need a vote to release an alpha (or beta, or RC)build, only a vote on declaring something stable.Yoav--- Jacob Kjome <[EMAIL PROTECTED] > wrote:> Quoting Mark Womack <[EMAIL PROTECTED]>:>> > This i

[VOTE] log4j 1.3 alpha 7 release

This is vote to decide if the current build of log4j 1.3 alpha 7 should be released. If accepted, the build located at: http://cvs.apache.org/builds/logging/log4j/log4j-1.3a7/ would be moved to the release area, with the related signed versions, and the related download pages would be updated a

1.2.13rc1 build

- expanded test case to include more TRACE coverage - updated HISTORY.txt - updated build.xml to 1.2.13rc1 - Created a v1_2_13_rc1 tag in svn Build can be accessed from: http://cvs.apache.org/builds/logging/log4j/log4j-1.2.13rc1/ I used the same build environment, so everything should be ident

Re: DO NOT REPLY [Bug 37122] - Console redirection in 1.2.12 causes infinite loop in JBoss

Curt, Thanks.  I will look into building 1.2.13rc1 tonight with this fix and the TRACE fix (and wider set of unit tests). -MarkOn 10/19/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT

Re: 1.3 alpha 7 build

no install-chainsaw.xml either.Thanks,Gary> -Original Message-----> From: Mark Womack [mailto: [EMAIL PROTECTED]]> Sent: Wednesday, October 12, 2005 9:15 PM> To: Log4J Developers List> Subject: 1.3 alpha 7 build>> As promised, here is the 1.3 alpha 7 build.>> I think I t

  1   2   3   4   >