Still, same error. Any advice? Can I get SVN to produce more error detail?
I use the cmdline:

svn checkout http://svn.apache.org/repos/asf/logging/log4j/branches/v1_2-branch/

Thanks,

Sagi Mann

________________________________


From: Paul Smith [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 20, 2007 12:36 PM
To: Log4J Developers List
Subject: Re: JUL appender



This is the correct URL for downloading via svn:

http://svn.apache.org/repos/asf/logging/log4j/branches/v1_2-branch/

cheers,

Paul

On 20/06/2007, at 5:27 PM, Sagi Mann wrote:





Scott,

Where can I find information on setting up SVN for use with Apache's SVN server?

I'm using SVN 1.4.4 and unable to initially checkout from:

http://svn.apache.org/viewvc/logging/log4j/branches/v1_2-branch

error is:

svn: PROPFIND request failed on '/viewvc/logging/log4j/branches/v1_2-branch'

svn: PROPFIND of '/viewvc/logging/log4j/branches/v1_2-branch': could

not connect to server (http://svn.apache.org)



Maybe I need a username other that guest?

thanks,



Sagi Mann



-----Original Message-----

From: Scott Deboy [mailto:[EMAIL PROTECTED]

Sent: Monday, June 18, 2007 03:41 PM

To: Log4J Developers List [EMAIL PROTECTED]

Subject: RE: Jull Appender



We're currently integrating the 1.2 branch

(http://svn.apache.org/viewvc/logging/log4j/branches/v1_2-branch/)



with the 'companions' structure

(http://svn.apache.org/viewvc/logging/log4j/companions/)



So please provide patches against that codebase.



Scott Deboy

COMOTIV SYSTEMS

111 SW Columbia Street Ste. 950

Portland, OR  97201



Telephone:      503.224.7496

Cell:           503.997.1367

Fax:            503.222.0185



[EMAIL PROTECTED]



www.comotivsystems.com







-----Original Message-----

From: Sagi Mann [mailto:[EMAIL PROTECTED]

Sent: Mon 6/18/2007 5:21 AM

To: log4j-dev

Subject: RE: Jull Appender



Hi Scott,

I'm using the 1.2.14 package. Based on the URL you sent, seems like I

need the 1.3 package to get going. How do I get all the 1.3 code? I

have SVN, but I'm not sure of the checkout cmdline. Where can I find

this info in log4j site?

thanks.



Sagi



-----Original Message-----

From: Scott Deboy [mailto:[EMAIL PROTECTED]

Sent: Thursday, June 14, 2007 08:29 PM

To: Log4J Developers List; [EMAIL PROTECTED]

Subject: RE: JUL appender



Great!



The tests you'd write aren't quite like the tests we've got (at least

that I could find), but here is the link to what we have:



http://svn.apache.org/viewvc/logging/log4j/trunk/tests/src/java/org/apac

he/log4j/



You'd need to use a memoryhandler on the java.util.logging side and

assert that an event sent by log4j was received by the memoryhandler.



Good stuff!



Scott Deboy

Principal Engineer

COMOTIV SYSTEMS

111 SW Columbia Street Ste. 950

Portland, OR  97201

Office: 503.224.7496

Direct Line: 503.821.6482

Cell: 503.997.1367

Fax: 503.222.0185

[EMAIL PROTECTED]

www.comotivsystems.com



-----Original Message-----

From: Sagi Mann [mailto:[EMAIL PROTECTED]

Sent: Thursday, June 14, 2007 10:22 AM

To: log4j-dev@logging.apache.org

Subject: RE: JUL appender



Scott,



Ok great, I've added the information and uploaded the code to issue

42664. I don't have unit tests at the moment. If there are any

existing unit tests I can read for reference, I'd be happy to provide

unit tests for the appender. Any advice where I can find any?



thanks.

-sagi



-----Original Message-----

From: Scott Deboy [mailto:[EMAIL PROTECTED]

Sent: Thursday, June 14, 2007 06:46 PM

To: Log4J Developers List [EMAIL PROTECTED]

Subject: RE: JUL appender



We need the current Apache license added to each source file,

Javadoc and comments where appropriate.



Scott Deboy

COMOTIV SYSTEMS

111 SW Columbia Street Ste. 950

Portland, OR  97201



Telephone:      503.224.7496

Cell:           503.997.1367

Fax:            503.222.0185



[EMAIL PROTECTED]



www.comotivsystems.com







-----Original Message-----

From: Sagi Mann [mailto:[EMAIL PROTECTED]

Sent: Thu 6/14/2007 8:39 AM

To: log4j-dev@logging.apache.org

Subject: RE: JUL appender



Hi Scott,



Thanks for the reply. Pls advise before I attach the code:

What do you expect (as a convention/requirement) I should prepare

along with the code? I'm not too sure about appropriate EULAs, doc

convention, etc.



thanks.



-----Original Message-----

From: Scott Deboy [mailto:[EMAIL PROTECTED]

Sent: Thursday, June 14, 2007 05:08 PM

To: Log4J Developers List [EMAIL PROTECTED]

Subject: RE: JUL appender







This is the place!







If you don't mind creating a bugzilla issue and attaching the

appender, it would help us review it (and find it later)







Here's the bugzilla link:



http://issues.apache.org/bugzilla/enter_bug.cgi?product=Log4j







If you don't want to go through that, you could attach to this mailing

list (but adding to bugzilla gives the highest likelihood it will be

reviewed).







Scott Deboy



COMOTIV SYSTEMS



111 SW Columbia Street Ste. 950



Portland, OR  97201







Telephone:      503.224.7496



Cell:           503.997.1367



Fax:            503.222.0185







[EMAIL PROTECTED]







www.comotivsystems.com















-----Original Message-----



From: Sagi Mann [mailto:[EMAIL PROTECTED]



Sent: Thu 6/14/2007 6:52 AM



To: log4j-dev



Subject: JUL appender







Hi all,







I'm new to this devlist. I've sent this email once before, but due to

some



email issues I realize it did not come through.







I was thinking of bridging JUL and log4j, so that existing log4j-enabled



applications could correctly write to JUL-enabled environments, with the



full layout/filter/handler log4j support. At the moment, using the



ConsoleAppender works ok, however, the log4j log levels are not mapped

to



JUL levels. For example, under Sun AppSrv 9.01, all log4j messages show

up



at the INFO (stdout) or WARNING (stderr) level, regardless of what

method



the application called. Anyway, I have created a JulAppender to solve

this



issue and I was wondering if this is the place to offer it to some sort

of



review or as a log4j addition; If so, what is the next step?







thanks,







- s



---------------------------------------------------------------------

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]



---------------------------------------------------------------------

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]






Paul Smith
Core Engineering Manager

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to