Very interesting dicussion in this thread. And it seems most people are in
favor
of using namespace as a single mechanism. It is true that using namespace is
the
most simple way to resolve conflict, but I insist that it is not the most
transparent
solution for users. That is because, IMHO,
WRT my message posted on 2005-08-30 14:46:38, I found that MS has a
known problem with Windows XP SP2. There seems to be a hot fix
available. Problem is described here:
http://support.microsoft.com/?kbid=892099
Cygwin version of rsh does not have the problem.
Michael Giroux
Try running without a CLASSPATH environment variable.
Maybe your CLASSPATH contains unquoted spaces (e.g., Program Files), or
ends in a backslash character.
Hope this helps
Keith
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 01 May 2006 15:50
To:
On 5/2/06, Huxi LI [EMAIL PROTECTED] wrote:
[...] but I insist that it is not the most transparent solution for users.
It is in fact too transparent, so transparent that users or
maintainers of the build scripts have a hard time figuring out where
the tasks are coming from or what they do. The
I've got an sshexec command that calls a remote script. The remote
script can take something like 5-15 minutes to run. Trouble is, the
sshexec never detects that the script exists. What have I done wrong?
Carlton Brown http://web.snt.bst.bls.com/db/emp/bwwhbhp
BellSouth Science
Did you mean to say ...ssh never detects that the script exits... ?
What OS are you executing the script on? Can you send the relevant
portion of your build.xml please? What version of ssh server are you
running? Also, try to see if you can get a script to return that takes
like 2 min, 3 min,
Try first with a simple command (like ls). Check if your command
requests for input or output. Does your command spawns background
processes (for example, starting a web server)? If so, does it redirect
stdin, -out, -err streams (for example, nohup does not always do
that)? Can you try to
Hi,
2006/5/3, Brown, Carlton [EMAIL PROTECTED]:
I've got an sshexec command that calls a remote script. The remote
script can take something like 5-15 minutes to run. Trouble is, the
sshexec never detects that the script exists. What have I done wrong?
Which ant version are you using?
Hello,
I created a sourceforge project called antcount
(http://antcount.sourceforge.net/). Antcount is a set of Ant filters
used for gathering statistic information from files or resources.
I already added a reference to it in the AntExternalTaskdefs Wiki
page. I'd like to know if it is
So you factor compilers/linkers rather than definesets. --DD
Is there more information on this or using a refid for the defineset? For
the way our build environment is set up, the easiest solution would be the
refid for a defineset. I've been looking into the compiler option, but I'm
not
I'm not having any luck. I recall from the message referenced below
that at the time, the verify stage read CLASSPATH, not the classpath
attribute of the rmic task. Is that still true?
On 4/27/06, Alexey N. Solofnenko [EMAIL PROTECTED] wrote:
rmic's classpath should be the whole classpath from
This is what I do, and it works fine with ANT nightly (but 1.6.5 should
be fine too):
rmic classpath=${javac-classpath} debug=true
includes=${rmic-sources} base=${classes-output} stubversion=1.2 /
${rmic-sources} - a list of all .class files that need stubs.
- Alexey.
Aaron Davies wrote:
Hello. I'm trying to use the property task with a prefix. Here is the
code I'm using:
--
property file=./webtest.properties prefix=${env} /
echo message=host: ${host} /
--
And here is the properties file I'm
Well sure, if you know ahead of time what needs stubs it's going to
work! :-) I'm trying to fix the build file for a large team project
where I have no idea what's implementing Remote and what isn't. Isn't
this what the verify attribute is *for*?
On 5/2/06, Alexey N. Solofnenko [EMAIL PROTECTED]
Hmm... How did they build it before? Maybe there is a list somewhere in
IDE project files.
- Alexey.
Aaron Davies wrote:
Well sure, if you know ahead of time what needs stubs it's going to
work! :-) I'm trying to fix the build file for a large team project
where I have no idea what's
Looks like you've got prefix backwards. When you set
env to localhost and load this file, you should end up
with property settings:
localhost.localhost.host=localhost
localhost.qa.host=qatest.domain.com
Ordinarily you would probably set up
localhost.properties and qa.properties files, and use
I'm not sure about the answer to your original question but I might be able
to suggest a different way to accomplish what you are trying to do. Someone
on this mailing list, probably Jan Materne, gave me the basic idea and it
worked very well in my build script.
The purpose of my script is to
AFAICT it's always been like this. This is a warning, not a fatal
error, but it's an annoying one that clutters up the build logs.
On 5/2/06, Alexey N. Solofnenko [EMAIL PROTECTED] wrote:
Hmm... How did they build it before? Maybe there is a list somewhere in
IDE project files.
- Alexey.
path id=compile.classpath
fileset dir=${local.dir}/lib includes=${local.compile.libs} /
fileset dir=${repository.dir} includes=${repository.compile.libs} /
/path
with maybe changing your separator to the one 'includes' uses (space
and/or comma I think. I'm unsure it will accept semi-colon or
Huxi LI wrote:
Very interesting dicussion in this thread. And it seems most people are in
favor
of using namespace as a single mechanism. It is true that using
namespace is
the
most simple way to resolve conflict, but I insist that it is not the most
transparent
solution for users. That is
Trent Ohannessian wrote:
Hello. I'm trying to use the property task with a prefix. Here is the
code I'm using:
--
property file=./webtest.properties prefix=${env} /
echo message=host: ${host} /
--
And here
Aaron Davies wrote:
AFAICT it's always been like this. This is a warning, not a fatal
error, but it's an annoying one that clutters up the build logs.
we could downgrade it. I have to ignore it on a regular basis too.
-
To
I suppose that's one solution, but wouldn't fixing the problem be a better one?
On 5/2/06, Steve Loughran [EMAIL PROTECTED] wrote:
Aaron Davies wrote:
AFAICT it's always been like this. This is a warning, not a fatal
error, but it's an annoying one that clutters up the build logs.
we could
Hello All,
I have a requirement of checking out files from StarTeam
only if the Label is frozen.
StarTeam Doesnt provide a way to check the Status of
a Label (Frozen or not) using StarTeam Client. So I have written a Java class
to get the status of label with Custom ANT Task. Now I
Surely the java task can create a property file for the host build.xml
to read; a judicious hit of 'antcall' and 'depends' should be able to
inhale it as needed
js
-Original Message-
From: Guttula, Mohan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 02, 2006 4:34 PM
To: Ant Users List
25 matches
Mail list logo
