Your failure was thinking in "variables" not in "Ant properties".
Later are immutable - once set they cannot change. (exception: )
Jan
>-Ursprüngliche Nachricht-
>Von: Scot P. Floess [mailto:sflo...@nc.rr.com]
>Gesendet: Dienstag, 24. November 2009 22:19
>An: Ant Users List
>Betreff: Re:
Sorry, you will probably need to use 2 properties for each call to
dirname...
On Tue, 24 Nov 2009, Scot P. Floess wrote:
You can run dirname task twice... First dirname will cut out four, the
second dirname will cut out three...
On Tue, 24 Nov 2009, jhudson wrote:
Hi
I have below re
You can run dirname task twice... First dirname will cut out four, the
second dirname will cut out three...
On Tue, 24 Nov 2009, jhudson wrote:
Hi
I have below requirement in ANT:-
variable1 = ${basedir}
now let us say from above statement "variable1" got the value
C:\one\two\three\four
Hi
I have below requirement in ANT:-
variable1 = ${basedir}
now let us say from above statement "variable1" got the value
C:\one\two\three\four
now i want to cut two levels from above path (so "C:\one\two" will be the
result after cut) and i want to reassign the value to varibale1.
So, if
If only i had listened :) Thank you for your help all working perfectly.
On 24 Nov 2009, at 19:49, Greg Roodt wrote:
batchtest
-
To unsubscribe, e-mail: user-unsubscr...@ant.apache.org
For additional commands, e-mail: user-
It will depend on the OS that you are running and grabbing the PID. In most
unix systems, the PID of the last executed process is in the variable $!. You
can store this in a file for later retrieval if necessary. You can also add a
very specific -D property and then use a combination of the ps,
Ready to try my suggestion?
Have you tried setting the failure properties on "batchtest" rather
than the "junit" task?
On Tue, Nov 24, 2009 at 7:47 PM, Ben Cuthbert wrote:
> I see. And yes it is firing them now. But I am back to the old problem that
> the build does not fail when there is an e
I see. And yes it is firing them now. But I am back to the old problem
that the build does not fail when there is an error
Ant has resolved your variables references.
Your "if" should look like this:
On Tue, Nov 24, 2009 at 7:32 PM, Ben Cuthbert wrote:
> Yes I got the following error running in debug
>
> test-unit:
> Skipped because property 'true' not set.
>
>
> ant build -Dunit.test=true -verbose
>
> What is th
Yes I got the following error running in debug
test-unit:
Skipped because property 'true' not set.
ant build -Dunit.test=true -verbose
What is the property true
On 24 Nov 2009, at 14:42, glenn opdycke-hansen wrote:
Suggest that you run in verbose mode. i suspect that the target
could be
You might have better luck if you use the and as
subclauses. It makes it easier to see what you're doing:
[]
You realize that excludes actually override your includes in this
manner? That is, *.java files in **/xpush/**" will be excluded. Is
this what
what about pkill on the ant process itself?
On Tue, 24 Nov 2009, Harry_ wrote:
Hello,
I want to schedule a task using ant using crontab.
On shell script will start the ant and the task I want to run. This is easy.
One shell script will kill the above ant process.
But the problem is that m
Hello,
I want to schedule a task using ant using crontab.
On shell script will start the ant and the task I want to run. This is easy.
One shell script will kill the above ant process.
But the problem is that multiple java processes are running on machine. I
only want to kill only the ant pro
So, problem solved? Or still unresolved?
On Tue, 24 Nov 2009, durbans wrote:
Sorry, I was wrong.
--
View this message in context:
http://old.nabble.com/Regular-expression-in-%3Cpropertyregex%3E-tp26498126p26498505.html
Sent from the Ant - Users mailing list archive at Nabble.com.
---
Sorry, I was wrong.
--
View this message in context:
http://old.nabble.com/Regular-expression-in-%3Cpropertyregex%3E-tp26498126p26498505.html
Sent from the Ant - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-m
Are you sure INPUT_TEXT is set? I've used propertyregex with properties
and it never took the string literal of the property name, curly braces
and $ sign... You might echo INPUT_TEXT before the call to propertyregex
to ensure you are, in fact, setting that property...
On Tue, 24 Nov 2009,
durbans wrote:
>
> input="${INPUT_TEXT}"
> regexp=""
> select="\2"
> casesensitive="true" />
>
>
Sorry I found that I have a bit different problem
: How can I use a variable in input parameter ?
It seems that if I write
http://old.nabble.
I believe cobertura has a third level version. I think the latest version
is 1.9.2. As a note, I have been starting to use the website
http://www.jarvana.com to search for dependencies. It's pretty useful if
you know the library you want and when you click on the information link, it
will give y
I have a string on more lines, like:
AAA THIS IS A
A
CCSTRINGCCC TODAY CC
D GREP ME NOW DD
I want to "grep" with ANT propertyregex the word "TODAY".
What should i put on regexp field to extract the word TODAY ?
I want to IGNORE every character
Suggest that you run in verbose mode. i suspect that the target could be
the cause.
-glenn
That's exactly what I ended up using. I cross-posted this on stack overflow
and someone gave me the idea their as well. I'm still curious about why
replaceregexp is not noticing the "\n' character. One day when I have the
time I will look into it a bit more.
foamdino wrote:
>
> Hi,
>
> I just
Strange if i put in the changes as you suggested it does not even execute my
targets. If I run the following on the command line
ant build -Dunit.test=true
On Monday, November 23, 2009, at 09:52PM, "glenn opdycke-hansen"
wrote:
>I agree that there is nothing obviously incorrect. However, do
Hi,
I just had to strip blank lines from a file the other day, try this:
http://ant.apache.org/manual/CoreTypes/filterchain.html#linetokenizer
Kev
-
To unsubscribe, e-mail: user-unsubscr...@ant.apache.org
For additional command
23 matches
Mail list logo
