We've found the missing-link tasks to be really helpful - doesn't appear
to be under active development any more though.
https://missinglinkcode.wordpress.com/ points to a dead Google Code repo
now, but a recent comment from the developer points to
https://github.com/alex-sherwin/missing-link/
On
Is there an easy method of capturing the exact response when using the
"http" condition? Given a task like this:
...it'd be nice, in a project I'm working on at the moment, to be able to
return more granular error messages than "boo, HTTP error!" and "yay, no
HTTP erro
Hi,
I tried to use the following in 1.9.2:
where $output is a plain text property supplied to the build, expecting to
get four new directories, each created under the previous, and to have
four accompanying ids to refer back to them later with.
Instead the ids resolve to things like
"C:\
ecure input handler
On 2013-08-30, Tom Cleghorn wrote:
> When using the secure input handler - e.g.:
>
>
>
> ...the build hides the keyboard input as expected. However, if I run ant
> with -d, the next line of console output is "Setting project property:
pwd
> -&
Hi,
When using the secure input handler - e.g.:
...the build hides the keyboard input as expected. However, if I run ant
with -d, the next line of console output is "Setting project property: pwd
-> pass"!
This seems less than ideal - is it by design, and are there any steps I
can take
Hi,
I'm puzzled by the new if and unless functionality - it seems that in
1.9.2, the following, where ${id}.css *does* exist:
...will set $has.css.overrides to 'true' as expected, but the property
won't then evaluate as (boolean) true for this:
Is this expected behaviour? If I use if:set, th
