Hola,
As a user of both Nagios and log4j, I'd be very interested in this.
Yoav
On 1/22/07, Jar Lyons <[EMAIL PROTECTED]> wrote:
Log4j Community,
I have just updated my sourceforge project for the NagiosAppender
(http://sourceforge.net/projects/nagiosappender), and I would like to
know if there
Hi,
No, the ASF does not require a CLA from people contributing patches
via an issue tracker. Only committers. If contributors want to sign
a CLA, they can, but it's by no means required.
Yoav
On 11/20/06, Scott Deboy <[EMAIL PROTECTED]> wrote:
Does LS or Apache -require- a CLA from one-time
Hi,
On 11/20/06, Jacob Kjome <[EMAIL PROTECTED]> wrote:
Congratulations Elias! You are the newest committer of the Log4j
team. Welcome!
Yoav, Curt, or someone else in the know about infrastructure
stuff; can you get Elias set up properly?
Welcome aboard Elias! ;)
The rough order of infras
Remember values as
bookmarkable template".
Is there something wrong with my user profile?
Thomas Raddatz.
Yoav Shapira schrieb:
> Hi,
> Click the "Create a new attachment" link under the Summary field, and
> follow the directions there.
>
> Yoav
>
> On 11/20/06, Th
Hi,
Click the "Create a new attachment" link under the Summary field, and
follow the directions there.
Yoav
On 11/20/06, Thomas Raddatz <[EMAIL PROTECTED]> wrote:
Curt,
How do I attach a file to a bug report? Do I have to use the "URL:" field?
http://issues.apache.org/bugzilla/enter_bug.cgi?p
Hi,
This is just an FYI to projects whose releases I've signed in the
past. Nothing urgent, and no action required on your part. Phil, I'm
also CCing you as I believe I signed your key with my old bad one -
sorry about that.
PGP went nuts on me last week, and after a couple of days of trying to
Good, then let's start a vote.
BTW, Curt's view on CLA before committer nomination, while pragmatic,
is not reflective of all ASF projects or the guidelines. Every other
ASF project I've been involved with nominated committers as they see
fit, and if after nomination the committer can't sign a C
Hi,
+1 to Elias as a committer.
Jake, don't worry about formalities ;) The only minor thing I would
have done is put [VOTE] at the beginning of the subject line, as
that's somewhat of a tradition. But it's not important enough to
start a new thread or change the topic of this one. When this vo
Hi,
On 11/12/06, Jacob Kjome <[EMAIL PROTECTED]> wrote:
Maybe its time for new blood? If existing Log4j developers can't put
in the time necessary to move things along as fast as the community
would like, then it might be time to accept some new developers from
the community that are willing t
It's been quiet, I imagine others (like me) are busy. These
outstanding issues you're talking about, do they have patches attached
in Bugzilla?
Yoav
On 11/12/06, Elias Ross <[EMAIL PROTECTED]> wrote:
Perhaps the committers left for a sabbatical, but I was wondering if Log4J
development is sti
Hi,
On 9/14/06, Curt Arnold <[EMAIL PROTECTED]> wrote:
I'm fine with tagging site to reflect its state at the time of log4j
1.2.14 release. Since its content doesn't affect log4j-1.2.14
itself, I'd like to tag it as the new content is pushed out assuming
a favorable vote on the release of log4j
Hi,
+1 to the release after some medium-strength testing (running it on a
dev server in an app that uses log4j for a couple of hours) and
looking at the distros.
Two comments:
On 9/14/06, Curt Arnold <[EMAIL PROTECTED]> wrote:
If release of the vote passes, the archives will be renamed to remo
Hi,
jmx-extra is not a jar, it's the property name. Set it to the
location of jmxtools.jar if you have it. The jmxtools.jar file is the
Sun JMX toolkit implementation (as opposed to the API jar). You can
get it from java.sun.com, read more about it at
http://java.sun.com/developer/JDCTechTips/2
Hi,
In the past I've downloaded JMS (API) from java.sun.com and put it
where the build.properties indicates. I was surprised by, but didn't
have time to pursue, the fact JMS should be optional and not cause the
build to fail.
Yoav
On 8/8/06, Ted Yu <[EMAIL PROTECTED]> wrote:
Hi,
Although JMS i
Hi,
Is there a formally tagged build newer than that rev ?
AFAIK no.
Also, how can I setup svn so that I can check out the
source ?
http://www.apache.org/dev/#svn.
Yoav
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For add
Hi,
Create it yourself, using something like this:
%svn co http://svn.apache.org/repos/asf/logging/log4j/[EMAIL PROTECTED] trunk
(you can also use the svn co -r switch if you prefer that syntax)
%cd trunk
%ant dist
That's it. I doubt we have a formally tagged built for that rev.
Yoav
On 8/8/
e you still show mid 2006 as a final release
- I guess that should be updated to late 2006.
Thanks,
Kris
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Yoav Shapira
Sent: Wednesday, July 26, 2006 3:00 PM
To: Log4J Developers List
Subject: Re: Alpha 9 rel
Hey,
We made a promise to our Marketing Department to have it out by today,
so we've all been working days and nights the past couple of weeks,
but unfortunately...
... just kidding of course. Like most other FOSS projects and
virtually all Apache ones, we don't have exact planned release dates.
+1.
Yoav
On 7/21/06, Elias Ross <[EMAIL PROTECTED]> wrote:
On Thu, 2006-07-13 at 14:09 -0700, Elias Ross wrote:
> This should get you the source.
>
> svn co http://svn.apache.org/repos/asf/logging/sandbox/log4j/concurrent
log4j-concurrent
>
> I'd like to put out a vote in the next week. I wo
Hi,
[OT] a good plaste to start with JUnit? if i remember weel it's for "black
box" testing while a log appender need to do some output
Google for any one of a million JUnit tutorials out there, including
on junit.org itself. And as previously mentioned, take a look at
existing tests to s
Hi,
You mean i submit a new bug?!?!?! i have an account... but i didn't see any
way to submit enhancement but only bug???
Open a "bug" and select "enhancement" under the severity field.
i'm a newbie of JUnit... what's the best way of testing a log4j appender???
Look at the existing unit te
Stefano,
Thanks for suggesting your contribution! We always welcome new
contributors and their work. See more comments inline:
http://www.entwash.org/hibernate/
so i take inspiration and made a Configurable Hibernate Appender... it's the
first time i develop an appender so i'm not sure of s
Diego,Thanks for contributing! In the future, when you have large attachments, it's better to put them in our issue tracker (http://issues.apache.org/bugzilla).The JExcel link on SourceForge doesn't work for me: it returns a 404 (file not found) error in the browser. There's a JExcel site at
htt
vn.apache.org)
Ready
Can you help me,
TIA,
Maciej
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Yoav Shapira
Nimalex LLC
1 Mifflin Place, Suite 3
ng choice not just now, but for a couple
of years in the future, given what we know about J2EE 1.5, the JVMPI /
JVMDI improvements in Tiger, and other similar opportunities to put
together new differentiating features, like loggers and appenders once
were...
Yoav
--
Yoav Shapira
Senior Architect
C, H3C 3J7, Canada www.ptidej.net
>
>
>
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Yoav Shapira
System Design and Management Fellow
MIT Sloan School of Management
Cambridge, MA, USA
[EMAIL PROTECTED] / www.yoavshapira.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
including me, ever thought
> about it.
>
> cheers,
>
> Paul
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Yoav Shapira
System Design and Management Fell
on.
>
> JDK 1.3 seems to be a reasonable target to me. To support JDK 1.4 as
> a target, there would have to be some specific benefit identified.
>
>
>
>
>
>
>
> ---------
> To unsubscribe, e-mail: [EMA
I've done this! :)
>
> cheers,
>
> Paul Smith
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Yoav Shapira
System Design and Management Fellow
MIT Sloa
not pushing hard for the release, especially since I haven't been
heavily involved with the compatibility stuff. My original message
was intended to be in the "by the way, here's something to think
about..." tone.
--
Yoav Shapira
System Design and Management Fe
gt; For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Yoav Shapira
System Design and Management Fellow
MIT Sloan School of Management
Cambridge, MA, USA
[EMAIL PROTECTED] / www.yoavshapira.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
>Should we include the latest compatibility report?
That would be a nice touch...
Yoav
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
ore
active in both talk and action, stuff has been getting back in.
--
Yoav Shapira
System Design and Management Fellow
MIT Sloan School of Management
Cambridge, MA, USA
[EMAIL PROTECTED] / www.yoavshapira.com
-
To unsubscribe, e
volvement from the community and more doc RFEs in Bugzilla. No
documentation is ever perfect, and there is plenty of room for
improvement of course, but I think log4j's documentation is not bad
considering its audience of developers/engineers concerned about
low-level details like logging.
> But t
---------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Yoav Shapira
System Design and Management Fellow
MIT Sloan School of Management
Cambridge, MA, USA
[EMAIL PROTECTED]
--
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Yoav Shapira
System Design and Management Fellow
MIT Sloan School of Management
Cambridge, MA, USA
[EMAIL PROTECTED] / www.yoavshapira.com
ts of concurrency.jar worth examining for the ones of you that
> are heavily into the innards of log4j, are possibly:
> ConcurrentHashMap
> ConcurrentReaderHashMap
> ReadWriteLock
> and obviously
> Sync and Mutex possibly along with CondVar
>
> Regards,
> Endre.
>
ni project moving again? Any suggestions?
>
> Ralph
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Yoav
> Shapira
> Sent: Thursday, December 01, 2005 12:16
> To: Log4J Developers List; [EMAIL PROTECTED]
> Subject: Re: log4jMin
with the main log4j project. I would
> like to see about getting that checked in as well.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
aven for builds instead of ant?
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Yoav Shapira wrote:
> > Hi,
> Hey,
> > -0.5 on using Maven. My experience with it has been that it's kind of
> > nice for generating project documentation, but for most
; Incidentally JmDNS has now relicensed themselves under ASL 2.0, which
> is good news for some auto-discovery stuff I'll be working on:
>
> http://sourceforge.net/forum/forum.php?forum_id=505375
>
> I take it hosting an ASL 2.0 jar inside the CVS repo is ok?
>
> ch
d pages would be updated accordingly (PMC approval, of
> > course).
> >
> > I am +1.
> >
>
> +1, although does an alpha really need a vote?
>
> Jake
>
> > -Mark
>
>
>
>
> ------
Hi,
-0.5 on using Maven. My experience with it has been that it's kind of nice for
generating project documentation, but for most real-life (i.e. complex
dependencies, multiple builders on different environments) projects, the setup
overhead is not worth the benefits.
It is also not as widely use
Hi,
> To make it clear:
> I was expecting it at
>
> http://www.ibiblio.org/maven/log4j/jars/
>
> and there it is. Provided at 23-Sep-2005 16:00. That is before
> I wrote the first mail. So as I said - I am the one who seems to be blind.
> So are we talking about minotaur.apache.org now?
minotau
Mark,
>From our perspective as Apache to committers, there is a specific directory on
minotaur.apache.org into which we copy distributions and they get mirrored in
ibiblio and other Maven repositories. The directory, if I recall correctly, is
/www/www.apache.org/dist/java-repository/[project name]
Hi,
I'd blast it out, it's just an alpha.
It's unfortunate that we've come to think of the release voting process as
arduous. It should be an easy thing, 72 hours, that's it.
Yoav
--- Mark Womack <[EMAIL PROTECTED]> wrote:
> Well, since the migration is taking longer than expected, I can loo
Hi,
> I agree, but I'm worried about the fact that our user base would rightfully
> be ticked if we forced them to change something that didn't have to change:
> terminology vs. semantics. We have a large user base using configs with this
> terminology - let's not make life difficult on them when
Hi,
Don't do it. It's a long discussion still under way, a topic of heavy debate,
but the safe answer is don't do it. You can join legal-discuss for specifics.
If the dependency is optional, i.e. the program will build and run without the
LGPL code, and you specify the LGPL code in the NOTICE fi
Hola,
I'm flying to Israel this evening for vacation, and email access will be
sporadic. I have one comment below:
> 3) Added a new jar that has the jndi related classes.
>
> Because I was now compiling with jdk 1.2, the jndi related classes
> were not available (?). So, I added a new propert
Hi,
> I wholeheartedly agree. Dropping 1.2 support "just because it's old" is
> very silly - there must be some -reason- behind that choice.
>
> Regards,
> Endre
True, but the reason doesn't have to be technical. If, for a given log4j
release, the marginal cost (in terms of developer time spen
Hola,
+1 on JDK 1.3. It's more than five years old now. If someone hasn't
updated their JVM in 5 years, they're not going to update log4j from 1.2...
Yoav Shapira
System Design and Management Fellow
MIT Sloan School of Management
Cambridge, MA USA
[EMAIL PROTECTED] / www.
dled into JDK 1.3, but a
> quick search did not come up with a jar for JDK 1.2.
http://java.sun.com/products/jndi/downloads/index.html, click on the
"Download JNDI 1.2.1" link.
Yoav Shapira
System Design and Management Fellow
MIT Sloan School of Management
Cambridge, MA USA
[EMAIL PR
Yuppdy doo, +1.
Yoav
Quoting Mark Womack <[EMAIL PROTECTED]>:
I move that we release log4j 1.2.12rc3 as the official release of v1.2.12.
We have addressed a number of annoying bugs, we have added the TRACE level.
The rc candidates have been made available to the user base via email
announcemen
Hi,
> > I was a bit surprised to see HISTORY.txt having separate entries for
> > log4j 1.2.12-rc1 and rc2 since those builds don't have the
> > endorsement of the the project and will never be part of the official
> > history of log4j. In the next build, I'd wrap all the chances since
> > 1.2.11
ormat, the user configuration format
in their webapp is up to them. That part of the assertion in the post you
quote is false.
However, the doc isn't perfectly clear on this. I should probably clarify
it further.
Yoav Shapira
System Design and Management Fellow
MIT Sloan School of Managemen
Hi,
> 14551, 17227, 18122, 30804, 30819 are Javadoc related.
I've fixed these on the 1.2 and HEAD branches.
> 26345 - may be too dangerous, need to review some more. Opinions?
Save for 1.3.
> 34026 - I think we should still fix this. Opinions?
Minor use-case, save for 1.3.
My goal is still
Hi,
I use PuTTY all the time, including yesterday and today, without problems.
I did update to the latest PuTTY client (v0.58 IIRC) a couple of weeks ago
for an unrelated reason. I did not have to change any settings in my PUTTY
clients to get it to use ssh v2, or anything like that.
Yoav
g4j-dev, and it should be short as in 72 hours
from start to finish. But yes, we need a vote even for alpha/beta/rcs.
Yoav Shapira
System Design and Management Fellow
MIT Sloan School of Management
Cambridge, MA
[EMAIL PROTECTED] / [EMAIL PROTECTED]
> -Original Message-
> From: Mark
Hey,
I couldn't have said it better than Paul: I agree with everything he says.
This is not a good 1.2 candidate, but should be a requirement for 1.3.0.
Yoav Shapira
System Design and Management Fellow
MIT Sloan School of Management / School of Engineering
Cambridge, MA USA
[EMAIL PROT
Hi,
> What about just doing what the deprecation warning has been saying for all
> of the 1.2 release and getting rid of Category and Priority altogether in
> the 1.3 release? I think everyone has been fairly warned about it.
I've been itching to do just that. +1.
Yoav Shapira
.
And this is not some strange bit of social engineering ;) On the contrary,
I feel bad for having forgotten this...
Yoav Shapira
System Design and Management Fellow
MIT Sloan School of Management
Cambridge, MA
[EMAIL PROTECTED] / [EMAIL PROTECTED]
> -Original Message-
> From: Curt
Hi,
The downloads aren't working, either from the mirrors or from the main
apache site. Looks like a missing slash in the directory path between
"dist" and "logging" which results in a 404 error.
Yoav Shapira
System Design and Management Fellow
MIT Sloan School of Manage
Hi,
Hmm, I could swear the Releases section in http://www.apache.org/dev/ had a
thing about PGP usage. Basically, by signing a release you vouch that it's
legit.
Yoav Shapira
System Design and Management Fellow
MIT Sloan School of Management
Cambridge, MA
[EMAIL PROTECTED] / [EMAIL PROT
.
signFile myproduct.zip
Then you just need to input your PGP password.
Yoav Shapira
System Design and Management Fellow
MIT Sloan School of Management / School of Engineering
Cambridge, MA USA
[EMAIL PROTECTED] / [EMAIL PROTECTED]
> -Original Message-
> From: Mark Womack [mailto:[EMAIL P
Hi,
> This is not authorative, but I doubt that it will happen since the
> resource
> requirements for an "additional" JDK is immense. On brutus, a complete
> build
> consumed many hours, and filled up disk space like nothing else.
>
> Gump is currently in a state of flux, and I would suggest tha
Hi,
One other suggestion: ask the Gump folks if they're willing to set up runs
for us on these JDKs. They do so for other projects. What's in the run
depends on us: we craft an Ant script and tell them which target to call in
that file. They set up the environment according to our needs.
At lea
Hi,
> And the source headers still reference the 1.1 license. If we update the
> license, we will need to update all the source headers. I don't know the
> answer here. Ceki, Yoav, do you know the policy regarding the updating of
> the license with releases like this? I guess we can always ask
Hi,
> Yeah, and I think that is the reason I did not seriously join the
> discussion
> last time. There is a lot of other stuff going across that mailing list;
> more than I can filter through effectively. I don't know if it is
> warranted, but other commons projects have their own mailing lists
Hi,
> Is there a JCL mailing list? I looked at the jakarta mailing list html
> page, but did not find one listed under the common project (not between
> JServe and Lucene :-).
[EMAIL PROTECTED], same as other Jakarta Commons projects ;)
Yoav
---
Howdy,
I'll be incommunicado for the next ~10 days, no internet, nothing ;) As I
mentioned before, I have no strong objections to anything going on (release
numbering, bylaws changes, etc.). If need be Mark can be my proxy vote, but I
don't think that'll be necessary. Have a good weekend everyon
Hi,
I largely agree with Jacob and Elias. However, I don't like the 1.4/1.5
discussion: jumping version numbers confuses users, as I found out first
hand with Tomcat, even when there's good reasoning for it.
> > 1) Release 1.2.11 with JMS build fix, maybe some other critical fixes
> > (action ite
us issues that have
long-term impact on the project. It's not been business as usual.
Yoav Shapira
System Design and Management Fellow
MIT Sloan School of Management / School of Engineering
Cambridge, MA USA
[EMAIL PROTECTED] / [EMAIL PROTECTED]
---
Hi,
I suggest you read the rest of the threads (not just the original message
you quoted) before ranting further ;)
Yoav Shapira
System Design and Management Fellow
MIT Sloan School of Management / School of Engineering
Cambridge, MA USA
[EMAIL PROTECTED] / [EMAIL PROTECTED]
> -Origi
The Apache Logging Services team is sorry to announce that we are recalling
log4j version 1.2.10, due to procedural issues under discussion. Please
discard copies of the release and revert to 1.2.9.
We hope to make a new release, 1.2.11, available shortly. Its release notes
will contain more inf
Hi,
Obviously there are already enough -1's ;) Let's pull the release off the
server, as I don't think the current disclaimer is sufficient.
And let's start a separate thread to discuss dependence on slf4j. I wonder if
it can be done dynamically, with runtime discovery or a similar mechanism,
ra
Hi,
It would have been nice to have a vote on this release, no? ;)
No big deal. Thanks for putting it together so quickly.
Yoav Shapira
System Design and Management Fellow
MIT Sloan School of Management / School of Engineering
Cambridge, MA USA
[EMAIL PROTECTED] / [EMAIL PROTECTED
Hi,
> Perception is not everything. Reality is at least as important as
> perception. Moreover, not all recognition is good. For example,
> take McDonalds as a widely recognized brand which is not associated
> with quality. Few volunteer developers want to spend their time
> creating crappy produc
Hey,
> the name being an advantage, to someone like me, it is a severe
> disadvantage.
> But I suppose I'm in the minority.
It's hard to tell if you're in a minority of hating the JCL name. Others
might, I totally believe it. But they *recognize* it, and that's important.
> I actually like th
Hi,
> So, is the only concern the brand name "JCL"? It seems to be.
Yup.
> If the
> code is
> going to be completely different and not backwards compatible with the
> existing
> "JCL" it isn't really "JCL", so why call it "JCL"?
Because the brand name is powerful and will lead to rapid adoptio
Hi,
> >I have confidence in the people (mentioned earlier, including us, the
> other
> >Tomcat folks, etc.) and the Apache brand. The JCL code itself will be
> gone,
> >replaced with our new creation, called JCL 2.0 for branding and adoption
> >purposes.
>
> Sounds nice, but can it be done?
I t
Hola,
> How can we have confidence when the existing JCL causes so many
> problems for log4j users, especially when even the mere existence of
> these problems have been denied for so long? It seems unrealistic,
> doesn't it?
I have confidence in the people (mentioned earlier, including us, the o
Hola,
> JUL was probably never designed to be a front end but rather as the
Yup.
> Maybe we should consider an independent project acting as a facade for the
> existing alogging APIs. Comments?
I'd prefer a fixed Jakarta commons-logging over a brand new project. I see
a dead-end in the current
Boris,
Don't apologize for wasting our time ;) Ideas are always welcome,
especially when they're backed up with code as yours were. At the same
time, be prepared to accept (and hopefully act upon) responses that say "go
read the f'ing archives and then come back to us" ;)
There's always room for
Hi Asgeir,
Thanks for offering your opinion, but just so you know, the only binding
votes are those of committers ;) Opinions are welcome and encouraged,
however.
Yoav
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 01, 2005 3:16 AM
> To: l
Hi,
> Unfortunately having both activate (overriden by internal appenders)
> and activateOptions (overriden by existing custom appenders) can make
> it extremely complicated to have a complex appender that performs the
> exact same actions for both activate() and activateOptions(). I have
> no pr
Hi,
> [1] http://marc.theaimsgroup.com/?l=log4j-dev&m=110874743313972&w=2
> [2] http://marc.theaimsgroup.com/?l=log4j-dev&m=110875656008077&w=2
OK, thanks, that was very useful.
[] Accept the additions to the Appender interface [X] Refuse those additions
[ ] Abstain
I suggest the following:
Hi,
Can we have a complete list of the changes being voted upon please? I'd
like to see it in one place before I vote. I'd also like to make sure
alternatives are explored, although they probably have been already. For
example, have an AppenderActivity interface with isClosed/isActive, and have
Hi,
I'm fine with that, +0. I'm also fine with waiting until our SVN move to do
this type of reorganization, because SVN has additional facilities for
splitting subtrees under a project that are kind of nice for this.
Yoav
> -Original Message-
> From: Paul Smith [mailto:[EMAIL PROTECTED]
+1 from me as well ;)
Yoav
> -Original Message-
> From: Paul Smith [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, February 23, 2005 4:19 PM
> To: log4j-dev@logging.apache.org
> Subject: [VOTE]: Chainsaw as seperate module
>
> This is a formalization of the thread 'Chainsaw as seperate CVS
Hola,
I don't think we should subclass it as final. That's a radical measure far
beyond a recommendation, and we can't assume we know all the
use-cases/scenarios under which people might want to subclass Logger.
The above applies to most open-source code, especially utility-level stuff
like log4j
Hi,
> There has been so much conversion to subversion recently in other areas
> of Jakarta, and I'm sure I read an email somewhere that the goal was to
> have everyone over to SVN by the end of the year, but I wouldn't trust
> my memory on things...
You read correctly: Henri Yandell sent an email
Hi,
>Is there any way we could get the Jakarta PMC and/or the ASF Board to kill
>the Commons-Logging project once and for all?
I doubt it. There are strong supporters for JCL within and outside the ASF.
As usual, the critics tend to be louder than the supporters, but people are
voting by taking
Hi,
Awesome article. Thanks for writing it and for fixing the code sections. I
suggest you invite comments on commons-dev to see what the JCL people think.
Another useful addition would be an expanded section on how UGLI
approaches/solves these problems.
Yoav
-Original Message-
From: Ce
Hi,
No need to ask, just contribute ;) Help is always welcome. Look for places
where you see a need, and submit enhanced docs (or code, or whatever you want)
via Bugzilla.
Yoav
Quoting Edmon Begoli <[EMAIL PROTECTED]>:
> Hi,
>
> I am available to help with documenting, and maintaing the JMX A
Hi,
>Does this mean that servers like Weblogic JBoss are not properly
>implementing
>the servlet spec? For instance, Weblogic comes with Log4j in the classpath
>because it uses Log4j for logging. Whether or not I add log4j.jar to
>WEB-INF/lib, the one from the server is used. I believe there is
Hi,
>> I don;t know the internals of Tomcat now, but once upon a time, the whole
>> point of Catalina was exactly the above, and not a "Child First
>>Behavior". If
>> CFB is in place in Tomcat, it is because of this bad entropy, and Tomcat
>>is
>> then indirectly adding to it.
>No, it is because
Hi,
> Placing endorsed libraries in WEB-INF/lib is *not* recommended. In fact,
> Tomcat actively avoids loading at least some endorsed libraries from
> WEB-INF/lib (Not sure about all maybe Yoav can clarify?). By
> "endorsed", I mean stuff like javax.*, org.xml.*, org.w3c.dom.*, etc
Hi,
> One of the important features in 1.3 is that you no longer have to
> ship log4j.jar in WARs. The idea is to place log4j.jar in your
> server's common/lib or equivalent.
Some servers don't have a common/lib directory or equivalent. It's not part of
the J2EE or Servlet Specifications, and as
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 Gülcü <[EMAIL PROTECTED]> wrote:
>
> Anybody think it is a bad idea? If yes, any alter
Hi,
+1.
Yoav
--- Ceki Gülcü <[EMAIL PROTECTED]> wrote:
>
> Hello all,
>
> It is my honor and privilege to propose Curt Arnold as a log4j
> committer. Curt is the lead of the log4cxx project. He has made
> several quite significant contributions to the log4j project and is
> expected to continu
1 - 100 of 117 matches
Mail list logo
