...Regarding the last section about the XML-parser sending af single '\n' -
I belive that from at least XML 1.1 it is mandatory for XML-parsers to send
a single '\n' up to applications disregarding platform and actual EOL-marker
within input-files parsed (with the purpose of simplifying processing
Hi all,
I experience some funny stuff with the "exec" task, when I set the "output"
attribute. It very much appears to me as if the output-stream does not get
flushed. Tried 1.5.3 and some 1.6's.
(I continue to have little luck with searching the bug-database; keep
getting lists a numbers out -
ainly not I, who invented the
"break" term.
But of course, that is a long time ago. Opinions change.
Regards,
Morten Sabroe Mortensen
-Original Message-
From: Steve Loughran
To: Ant Developers List
Sent: 04-08-03 19:01
Subject: Re: "echo"-task, ignorable whitespace and
able whitespace and CDATA-elements
On Sat, 2 Aug 2003, Morten Mortensen
<[EMAIL PROTECTED]> wrote:
> It will break things? That, of course, is between "bad" and
> "annoing".
Largely on the side of "bad" IMHO.
> But technically, I am right?
Sure.
Stefan
-
Hi all developers,
It is really nice to have "ant -projecthelp" list all those targets with a
"description"-attribute on them. I use it a lot. Some nights I have dreams
about targets with scopes put upon them, non-public targets, targets not
beeing listed by their name when executing Ant-scripts,
j, Danmark
mailto:[EMAIL PROTECTED]
http://www.tietoenator.com
-Original Message-
From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
Sent: 31. juli 2003 08:54
To: [EMAIL PROTECTED]
Subject: Re: "echo"-task, ignorable whitespace and CDATA-elements
On Wed, 30 Jul 2003, Mort
ss that implements Condition,
it, and use it inside . Cannot get any simpler, right?
I haven't played with Ant 1.6 at all, so this is all in theory ;-)
If it doesn't work, complain to Peter Reilly who did this (great!) piece of
code ;-) --DD
> -Original Message-
> From: Mo
ct: RE: Implementing "conditions"
Is-file and is-dir exist already. It's called , which is both a
Task and a Condition. --DD
> -Original Message-
> From: Morten Mortensen [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 30, 2003 2:48 PM
> To: 'Ant Developer
Hi All,
Regarding the "condition"-framework, I miss stuff like "is-file" and
"is-dir". Hence I have implemented these as regular tasks setting a property
and then used the condition-framework to branch on the values of these.
But I would like e.g. "is-file" and "is-dir" to be conditions, that is
Hi all,
It would be nice, if the "echo" task worked a bit different - actually
*ignored* leading and trailing whitespace in the body of the text.
The reason is, that XML-pretty-formatters - which does not change the
semantics of the XML formatted relative to the specification - may alter the
act
nd
you now have prefixed properties with all variables expanded.
Not ideal, but two lines, and works. --DD
> -Original Message-
> From: Morten Mortensen [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 23, 2003 2:40 PM
> To: 'Ant Developers List'; '[EMAIL PRO
Erik
p.s. No need to get impatient after less than a day of posting to the
user list, especially on a weekend. Not to mention that this has been
answered numerous times on the list and the answer is surely in the
archives and most likely at the jGuru Ant FAQ, and also in the Java
Development
-Original Message-
From: Morten Mortensen
To: 'user@ant.apache.org'
Sent: 06-07-03 05:30
Subject: Q: Double-expansion - reading environment variables "dynamically"?
Given a defined property "x" assigned the name of an
environment-variable, how do I rea
13 matches
Mail list logo
