http://www.apache.org/~rubys/updatesite.log4
Note the mod to 'whoweare.html and the errors in poi...
- Sam Ruby
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
On 28 Mar 2002, Jason van Zyl [EMAIL PROTECTED] wrote:
I just looked, because I thought there was one, and there is a
category for BCEL.
I have created one with Pier's help just today, should have reported
here, I guess ;-)
Stefan
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For
On Thu, 2002-03-28 at 09:00, Stefan Bodewig wrote:
On 28 Mar 2002, Jason van Zyl [EMAIL PROTECTED] wrote:
I just looked, because I thought there was one, and there is a
category for BCEL.
I have created one with Pier's help just today, should have reported
here, I guess ;-)
:-) So
On Thu, 2002-03-28 at 01:14, [EMAIL PROTECTED] wrote:
Jason van Zyl [EMAIL PROTECTED] wrote on 28/03/2002 08:15:53 AM:
On Wed, 2002-03-27 at 17:13, Leo Simons wrote:
It has been brought up by many people that there
is no common way of organising subproject websites.
I propose we
Jason van Zyl [EMAIL PROTECTED] wrote:
On Thu, 2002-03-28 at 09:00, Stefan Bodewig wrote:
On 28 Mar 2002, Jason van Zyl [EMAIL PROTECTED] wrote:
I just looked, because I thought there was one, and there is a
category for BCEL.
I have created one with Pier's help just today, should have
On Thu, 2002-03-28 at 09:05, Berin Loritsch wrote:
-Original Message-
From: Leo Simons [mailto:[EMAIL PROTECTED]]
On Wed, 2002-03-27 at 17:13, Leo Simons wrote:
It has been brought up by many people that there
is no common way of organising subproject websites.
I
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]]
On Thu, 2002-03-28 at 09:05, Berin Loritsch wrote:
I would definitely like to see a Maven like system across
the projects
in Jakarta--even if the main site is not altered much. It would be
good to give the
On Thu, 2002-03-28 at 09:53, Berin Loritsch wrote:
The only thing I would want to customize are:
1) Project Logo
2) Project color-scheme
No problem :-)
That's it. I really don't think that is too much to ask. The
layout should remain constant without a doubt.
We are in agreement
On Thu, 28 Mar 2002, Berin Loritsch wrote:
Everything should definitely feel the same. However, color is
a definite clue that you have changed contexts. By drilling
down a Project's heirarchy, it helps to have a visual clue that
you are not at the same level you used to be.
Color
In message [EMAIL PROTECTED]
bm.com, Sam Ruby writes:
http://www.apache.org/~rubys/updatesite.log4
Note the mod to 'whoweare.html and the errors in poi...
I did a fresh checkout of jakarta-site2 and edited xdocs/whoweare.xml last
night, did the usual build docs/whoweare.html, and checked in
All,
I've been lucky enough to have benefited from a lot of the excellent
packages put out be this community, e.g. ANT/XERCES/LOG4J/XALAN/SOAP2.2/AXIS
etc etc, and I thank you all for that. Recently however my utilization of a
lot of Apache software has bitten me (commons-logging in AXIS in this
From: Morgan Delagrange [mailto:[EMAIL PROTECTED]]
Yes, the defining advantage to the commons-logging API that I see is
that
it
allows users to adopt a single logging implementation, which confers
real
What needs to be appended to that statement is ...if everyone codes to
the
-Original Message-
From: Leo Simons [mailto:[EMAIL PROTECTED]]
another lenghty post, so I'll start with a summary:
- color variations (and all other lf changes) should be
part of the original look-and-feel design. Giving
programmers free reign to do this spells disaster.
It would also be very nice if this were rolled into Maven :)
cheers,
- Leo
Well, at this point Adam, we don't so much has have a written guideline
for creating a Jakarta release, so adding versioning to a non-existent
guidelines poses something of a challenge :O)
Please please please
*gets the feeling that the project marketing campaign for Maven has
begun and wonders if he bought into a time share and singed up for a
free seminar by accident*
Leo Simons wrote:
It would also be very nice if this were rolled into Maven :)
cheers,
- Leo
Well, at this point Adam, we don't
On Thu, 28 Mar 2002, Jeff Schnitzer wrote:
From: Morgan Delagrange [mailto:[EMAIL PROTECTED]]
Yes, the defining advantage to the commons-logging API that I see is
that
it
allows users to adopt a single logging implementation, which confers
real
What needs to be appended to that
I guess you folk have seen so many adhoc suggestions that you tend to
attempt to form a consistent guideline out of them. I'm not convinced this
particular approach has sufficient merit, or that there aren't better ones,
it was just an idea I threw out based on initial findings. I am game to
- color variations (and all other lf changes) should be
part of the original look-and-feel design. Giving
programmers free reign to do this spells disaster.
It would be best to have the original designer of a
look and feel work this out. Very strictly.
:(
Seriously, I
and to think I haven't even downloaded it yet! :D
*gets the feeling that the project marketing campaign for Maven has
begun and wonders if he bought into a time share and singed up for a
free seminar by accident*
Leo Simons wrote:
It would also be very nice if this were rolled into
- Original Message -
From: Jeff Schnitzer [EMAIL PROTECTED]
To: Jakarta General List [EMAIL PROTECTED]
Sent: Thursday, March 28, 2002 2:12 PM
Subject: RE: Comments on the commons-logging API
From: Morgan Delagrange [mailto:[EMAIL PROTECTED]]
Yes, the defining advantage to the
On Fri, 29 Mar 2002 07:49, Andrew C. Oliver wrote:
*gets the feeling that the project marketing campaign for Maven has
begun and wonders if he bought into a time share and singed up for a
free seminar by accident*
The funny thing is that some of the people marketing maven haven't even
At 15:10 28.03.2002 -0600, Morgan Delagrange wrote:
Where is this world where everyone uses Log4J?
That world = (world - jakarta)
--
Ceki
My link of the month: http://java.sun.com/aboutJava/standardization/
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands,
Just as a heads up. There will be something that helps you manage version
information in jars in the next release (1.5). It semi-automates declaration
of library name and version and it also allows the jar to declare
dependencies on other libraries. It does this according the following spec.
- Original Message -
From: Ceki Gülcü [EMAIL PROTECTED]
To: Jakarta General List [EMAIL PROTECTED]
Sent: Thursday, March 28, 2002 3:18 PM
Subject: Re: Comments on the commons-logging API
At 15:10 28.03.2002 -0600, Morgan Delagrange wrote:
Where is this world where everyone uses
Jason van Zyl [EMAIL PROTECTED] wrote on 29/03/2002 12:53:36 AM:
On Thu, 2002-03-28 at 09:53, Berin Loritsch wrote:
The only thing I would want to customize are:
1) Project Logo
2) Project color-scheme
No problem :-)
The only other thing I've found handy is if there's no
Ceki Gülcü [EMAIL PROTECTED] wrote:
At 15:10 28.03.2002 -0600, Morgan Delagrange wrote:
Where is this world where everyone uses Log4J?
That world = (world - jakarta)
I tend to agree with Ceki! :) I never used it until I didn't move on from
Jakarta and went to do some real work for my
At 15:30 28.03.2002 -0600, Morgan Delagrange wrote:
I am pro-Log4J. I wish I lived in that Log4J-only world (until/unless
something better came along). Generally, commons-logging neither encourages
nor discourages use of Log4J. However, I would argue that it _does_
encourage Log4J a bit by
Berin Loritsch [EMAIL PROTECTED] wrote:
Attached is a small screenshot of the maven page with a white
header.
Aaah WINXPCRAP! :)
Pier
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Peter Donald wrote:
On Fri, 29 Mar 2002 07:49, Andrew C. Oliver wrote:
*gets the feeling that the project marketing campaign for Maven has
begun and wonders if he bought into a time share and singed up for a
free seminar by accident*
The funny thing is that some of the people marketing maven
- Original Message -
From: Ceki Gülcü [EMAIL PROTECTED]
To: Jakarta General List [EMAIL PROTECTED]
Sent: Thursday, March 28, 2002 4:14 PM
Subject: Re: Comments on the commons-logging API
At 15:30 28.03.2002 -0600, Morgan Delagrange wrote:
I am pro-Log4J. I wish I lived in that
Pete Donald wrote:
Anyways if there is a demand for this I can get it into the
ant1.5 codebase
earlier.
I think what there ought to be a demand for is a Jakarta wide code of practice for
declaring versions and dependancies, even if its only in documentation. I guess this
just adds a
On Thu, 28 Mar 2002, Ceki Gülcü wrote:
True. It does encourage it, but only initially. On the long run,
however, people will run into problems with their logging (as is
happening now). They will say this commons-logging+log4j stuff is too
complicated, we'll switch to JDK 1.4 logging, at
Ceki,
What about making clear that commons-logging is only supposed to be
used by other components so that the application developer picks
the logging API that suits him best?
Do you really believe that all application developers will use
Log4J? Or do you want to force them into doing that?
At 16:33 28.03.2002 -0600, you wrote:
Sun's me-too strategy is bound to fail. The question is whether the
bigger jakarta community is going to help us defeat JSR47 or stand in
the way.
That's a bit harsh, isn't it?
Hmm, maybe it is. What I am trying to say is that I would have liked
to
On Fri, 29 Mar 2002, Ceki Gülcü wrote:
At 16:33 28.03.2002 -0600, you wrote:
Sun's me-too strategy is bound to fail. The question is whether the
bigger jakarta community is going to help us defeat JSR47 or stand in
the way.
That's a bit harsh, isn't it?
Hmm, maybe it is. What I
Costin,
I think you have done a pretty good job on the log4j wrapper. However,
I am pretty stretched out as it is, so I can't really help with something
I don't particularly like. Besides, if people find commons-logging really
useful
they will build a community around it. What I say or think
At 00:57 29.03.2002 +0100, Paulo Gaspar wrote:
Ceki,
What about making clear that commons-logging is only supposed to be
used by other components so that the application developer picks
the logging API that suits him best?
That seems to be the intent of commons-logging. I have pointed out
the
-Original Message-
From: Ceki Gülcü [mailto:[EMAIL PROTECTED]]
I never suspected (nor suggested) that commons-logging effort
was dishonorable in any way. My contention is that it will
make life harder not easier. Nothing more, nothing less.
I think it may make life harder for
On Fri, 29 Mar 2002 12:13, Scott Sanders wrote:
-Original Message-
From: Ceki Glc [mailto:[EMAIL PROTECTED]]
I never suspected (nor suggested) that commons-logging effort
was dishonorable in any way. My contention is that it will
make life harder not easier. Nothing more,
On Fri, 29 Mar 2002 12:38, Ceki Gülcü wrote:
1) logging calls are made thousands of times so the indirection through
an equalizer API (like commons-logging) has a performance impact
Not in modern JVMs (read most almost all jdk1.3 impls).
As long as the underlying indirection (ie between
god no. The avalon group was already using a facade logger long before
commons was for much the same reason commons adopted one.
Is Avalon still using its own facade logger or changed to commons-logging?
I'm just wondering: How many Jakarta projects use this common-logging
package? What's
Sam Ruby [mailto:[EMAIL PROTECTED]] wrote:
I very much like xml-commons-which.
http://cvs.apache.org/viewcvs.cgi/xml-commons/java/src/org/apache/env/
It seems very useful, and I've only view it briefly [so I am no expert] but
wouldn't it be better if classes/packages known or
On Fri, 29 Mar 2002, Ceki Gülcü wrote:
The problem with logging is different because:
1) logging calls are made thousands of times so the indirection through
an equalizer API (like commons-logging) has a performance impact
Only for the logger that do not implement the interface :-) If
Hey, I'm a programmer myself ;)
as a reassurance:
the changes this discussion talks about will happen in jakarta-site2,
and will consist of backwards-compatible changes to site.xsl and
site.vsl. Projects that depend on jakarta-site2 will change to the
new look and feel automatically. For
44 matches
Mail list logo
