Jake, I'm not 100% sure if this is relevant, but I could not get the
SCP ant task to work (which uses JSch) without using certificate
authentication (see the build.xml in the chainsaw tree, in the
distribution target, it copies the distribution over scp).
If you set up SSH key authenticatio
Message-
From: Jacob Kjome [mailto:[EMAIL PROTECTED]
Sent: Tue 2/14/2006 12:15 PM
To: Log4J Users List
Subject: RE: chainsaw timestampFormat and relative dates
Quoting Scott Deboy <[EMAIL PROTECTED]>:
> On my WinXP box,
>
> In my $user.dir/.chainsaw/plugins directory, I ha
Quoting Scott Deboy <[EMAIL PROTECTED]>:
> On my WinXP box,
>
> In my $user.dir/.chainsaw/plugins directory, I have:
>
> commons-logging.jar
> commons-vfs-1.0-RC2.jar
> jsch-20050802.jar
> log4j-chainsaw-vfs.jar
>
> I'd hope later versions of jsch would work as well.
>
> In $user.dir/.ssh director
EMAIL PROTECTED]
www.comotivsystems.com
-Original Message-
From: Jacob Kjome [mailto:[EMAIL PROTECTED]
Sent: Tue 2/14/2006 10:23 AM
To: Log4J Users List
Subject: Re: chainsaw timestampFormat and relative dates
Ok, I should have verified first. I found out that the config file is
specify
EMAIL PROTECTED]
www.comotivsystems.com
-Original Message-
From: Jacob Kjome [mailto:[EMAIL PROTECTED]
Sent: Tue 2/14/2006 10:23 AM
To: Log4J Users List
Subject: Re: chainsaw timestampFormat and relative dates
Ok, I should have verified first. I found out that the config file is
specifyin
Ok, I should have verified first. I found out that the config file is
specifying a custom date format. Our official config file has the ISO8601
format, but that hadn't been put in place on the appserver. I was just
assuming that the ISO8601 format was what I was seeing. Whoops. I thought
that
We have a log4j configuration with a file appender having the conversion
pattern
%-14d{ISO8601} %-5p %c{3} - %m%n
This results in lines such as...
13/02 14:05:06 DEBUG ui.actions.MyAction - Some message
My chainsaw config has the following for timestampFormat...
dd/MM HH:mm:ss
This wor
