Rob,
Admittedly, this is an off the wall question, but are
your ssh server and client on the same win2k host?
Bill.
Anderson, Rob (Global Trade) wrote:
1. What OS are you running sshexec on?
Win 2k
2. What java version is ant running on ?
java version "1.4.2_07"
3. What s
> 1. What OS are you running sshexec on?
Win 2k
> 2. What java version is ant running on ?
java version "1.4.2_07"
> 3. What ssh server implementation and version are you connecting to
> (openssh?),
OpenSSH_4.0p1, OpenSSL 0.9.7g 11 Apr 2005
> 4. What OS is the ssh server running on ?
Win 2
Rob,
thanks for trying my test case.Your BUILD SUCCESSFUL result is encouraging.
I'm also running jsch-0.1.20, and ant-1.6.2, but something must be
different.
1. What OS are you running sshexec on?
2. What java version is ant running on ?
3. What ssh server implementation and version are you co
You can write a script to run ant:
ant -Dcommand="%*" %*
- Alexey.
Eric Wood wrote:
My build.xml sends email that states whether or not the build succeeded
or failed. I would like to include which target was invoked from the
command line, but I haven't found a built-in property for this. I w
My build.xml sends email that states whether or not the build succeeded or
failed. I would like to include which target was invoked from the command
line, but I haven't found a built-in property for this. I was using the
ant-contrib task and setting it to the target name for each target,
but
Jsch folks- A user reported this to the ant-user list, but part of the problem
appears to be with jsch. See below for details.
Thanks,
-Rob A
> -Original Message-
> From: Anderson, Rob (Global Trade)
> Sent: Friday, June 03, 2005 10:15 AM
> To: 'Ant Users List'
> Subject: RE: Connectio
I was able to run the build file successfully using Ant 1.6.2 with jsch version
0.1.16. This is not a known problem with sshexec. It may be a problem with
jsch. What version of jsch are you using? When I use jsch 0.1.20 is see the
same problem with the output, but I still see BUILD SUCCESSFUL.
For anyone who is interested, the solution I found to this problem is to add
the junit.jar and tools.jar(from the java jdk) to Global Entries on the
classpath tab in Eclipse's Window->Preferences->Ant->Runtime, rather than to
Ant Home Entries. The Eclipse ant editor will still give you a warning t
For anyone who is interested, the solution I found to this problem is to add
the junit.jar and tools.jar(from the java jdk) to Global Entries on the
classpath tab in Eclipse's Window->Preferences->Ant->Runtime, rather than to
Ant Home Entries. The Eclipse ant editor will still give you a warning t
hey, get in line like everyone else!
use correct time and dates.
i delete all annoying future dated posts
--- Bill Winspur <[EMAIL PROTECTED]> wrote:
> Synopsis
> I am running ant 6.1.2 on XP Pro and have a test
> case that produces SSH connection failures by repetitively
> running
I have done . JUnit is on the
classpath. And we have verified that the jar does in fact have Test.class.
--- Begin Message ---
To really ensure that JUnit is on Ant´s classpath, you could print it out
classpath: ${java.class.path}
But putting junit.jar into ${user.home}/.ant/lib should help.
I have done . JUnit is on the
classpath. And we have verified that the jar does in fact have Test.class.
--- Begin Message ---
To really ensure that JUnit is on Ant´s classpath, you could print it out
classpath: ${java.class.path}
But putting junit.jar into ${user.home}/.ant/lib should help.
> -Original Message-
> Thanks Murali,
> Yes, I had found SOS, but it seems too GUI for use in ant. CodeForge
> looks perfect.
> chad
Note that there is also a command-line version of SOS, and ant tasks for it. I
tried them out a while back (over a year ago), with fair-to-middling succe
"Rebhan, Gilbert" <[EMAIL PROTECTED]> wrote ..
>
> I've just detected that there are some condition tasks
> in package net.sf.antcontrib.logic.condition i may use.
>
> Those tasks are migrated from antelope, but are
> not mentioned in the manual of antcontrib
>
> manual =
>
> http://antelope.
The logic for this, Brent, is as follows:
HTH
Bill Rich wrote:
>
> Since properties are immutable I don't think you need to check to see if a
> property is set or not. Make sure you set the default after any other
> possible setting of the prop
I've just detected that there are some condition tasks
in package net.sf.antcontrib.logic.condition i may use.
Those tasks are migrated from antelope, but are
not mentioned in the manual of antcontrib
manual =
http://antelope.tigris.org/nonav/docs/manual/bk03ch05s02.html
Those tasks should b
Hi,
any existing task that allows to check whether
int a > int b
int a => int b
int a < int b
int a <= int b
??
i've tried with math task of antcontrib 1.0b2 but that task doesn't
support
such comparison, only +, -, * allowed as operand.
Or any script examples with javascript or beanshell ?
Since properties are immutable I don't think you need to check to see if a
property is set or not. Make sure you set the default after any other
possible setting of the property. If the property gets set then setting the
default will do nothing.
HTH Bill
-Original Message-
From: Peter Re
Since properties are immutable I don't think you need to check to see if a
property is set or not. Make sure you set the default after any other
possible setting of the property. If the property gets set then setting the
default will do nothing.
HTH Bill
-Original Message-
From: Peter Re
19 matches
Mail list logo