bear in mind that svn can use multiple connections to communicate,
and often asks you for each connection. I've seen this before,
usually it's only 3 times, and then it seems to work.
we use svn here at Aconex and I've seen it do that to me.
On 04/04/2007, at 4:32 PM, Jacob Kjome wrote:
A
At 12:47 AM 4/4/2007, you wrote:
>
>On Apr 4, 2007, at 12:37 AM, Jacob Kjome wrote:
>
>>
>> I checked out with a URL that looks like
>>
>> https://username:[EMAIL PROTECTED]/repos/asf/logging/log4j/trunk
>>
>
>I've never needed to specify username:password in the URL. Should
>only need creden
On Apr 4, 2007, at 12:37 AM, Jacob Kjome wrote:
I checked out with a URL that looks like
https://username:[EMAIL PROTECTED]/repos/asf/logging/log4j/trunk
I've never needed to specify username:password in the URL. Should
only need credentials on commit.
Then I modified download.xm
At 11:00 AM 4/3/2007, you wrote:
>Quoting Curt Arnold <[EMAIL PROTECTED]>:
>
>>
>> On Apr 3, 2007, at 12:47 AM, Jacob Kjome wrote:
>>
>> >
>> > I would add this to the download.xml xdocs, but it seems as if my
>> > commit rights have been, somehow, revoked. I can log into
>> > people.apache.org,
At 12:51 PM 4/3/2007, you wrote:
>
>On Apr 2, 2007, at 7:07 PM, Paul Smith wrote:
>
>log4j 1.3 in my opinion is stuck in a hopeless position. It is too
>incompatible with log4j 1.2.x to ever be recommended as a drop-in
>replacement for log4j 1.2 in a production environment. However, if
>you chan
Curt Arnold wrote:
On Apr 3, 2007, at 9:33 AM, Jess Holle wrote:
Largely I won't disagree.
That said, I think there is a point to having a new log4j version
that is almost entirely API (source and binary) compatible with log4j
1.2.14, but:
Has finer-grained synchronization and eliminates some
On Apr 3, 2007, at 9:33 AM, Jess Holle wrote:
Largely I won't disagree.
That said, I think there is a point to having a new log4j version
that is almost entirely API (source and binary) compatible with
log4j 1.2.14, but:
Has finer-grained synchronization and eliminates some possibilities
On Apr 2, 2007, at 7:07 PM, Paul Smith wrote:
At some point we can no longer ignore the decision about where 1.3
should go.
I am beginning to think that we should scale back 1.3 to be less of
the planned revolution and more of a substantial-update-but-
completely-backward compatible (to a
> -Original Message-
> From: Jacob Kjome [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 02, 2007 10:11 PM
> To: Log4J Developers List
> Subject: Re: 1.3 - A Line in the Sand
>
> At 07:07 PM 4/2/2007, you wrote:
> >At some point we can no longer ignore the decision about where 1.3
> >shou
Quoting Curt Arnold <[EMAIL PROTECTED]>:
>
> On Apr 3, 2007, at 12:47 AM, Jacob Kjome wrote:
>
> >
> > I would add this to the download.xml xdocs, but it seems as if my
> > commit rights have been, somehow, revoked. I can log into
> > people.apache.org, but can't seem to check anything in to Log4
On Apr 3, 2007, at 12:47 AM, Jacob Kjome wrote:
I would add this to the download.xml xdocs, but it seems as if my
commit rights have been, somehow, revoked. I can log into
people.apache.org, but can't seem to check anything in to Log4j
using TortoiseSVN. Any ideas? BTW, at such point
Largely I won't disagree.
That said, I think there is a point to having a new log4j version that
is almost entirely API (source and binary) compatible with log4j 1.2.14,
but:
1. Has finer-grained synchronization and eliminates some
possibilities that currently exist for deadlocks, etc.
Hi
I'm just an end-user of log4j, so I have no perspective on the internal
dev issues.
But from the POV of a programmer who uses log4j in many projects, I have
to say that it's pretty great the way it is!!
It may simply be that log4j as it currently stands is good enough for
the vast majority of
I think it's been said before that 1.3 may be more of a dead end
than anything else. Some interesting things went into it, but the
fact that it became so incompatible with Log4j-1.2.xx is a real
problem. Is it worth a release or do we just leave it as-is,
forever alpha, and move on to 2
14 matches
Mail list logo
