Hi Gerry,
> > I'm wary of using whitespace as a delimiter.
>
> Right now target names are delimited by white space.
OK, I should've seen that one coming :)
I should've been more specific: I don't like line separators (whatever you
defined them as) as delimiters for this kind of thing.
> If you
> I'm wary of using whitespace as a delimiter.
Right now target names are delimited by white space. Should we move to this
format?
I'm joking btw.
What I was proposing (though didn't state very well is that we adopt a clear
well defined way of handling whitespace in elements an
Hi Gerry,
> What do people think of this addition to the format of filesets?
Humm... I must admit I'm not crazy about it either, and I don't feel it is
all that much intuitive compared to what we have now. Ian's reasons sound
pretty important to me, too.
--
Tomas Restrepo
[EMAIL PROTECTED]
-
I agree with Ian on this one. Keeping the elements as
parsable XML that can be manipulated via XSLT or the
DOM seems like a good goal to maintain.
--- Ian MacLean <[EMAIL PROTECTED]> wrote:
> Gerry,
>
> This new format is much more readable and easier to
> type than before.
> The major downsid
Gerry,
This new format is much more readable and easier to type than before.
The major downside I see is for people writing tools to read and write
the build file - or using xslt to transform it. You can no longer rely
on just the Xml api;s to read and write the build file. There now needs
to
What do people think of this addition to the format of filesets? Look at
the element of the task. The task is my own
private task. I thought it would be better to include the entire buildfile
in full so that if people could come up with a better syntax they could edit
the file.
Basically I'
