Hey that's good news! :)
Raagu wrote:
>
> I got it. We should write ${line.separator} as delimiter attribute value.. It
> works..
>
>
>
>
> Scot P. Floess-2 wrote:
> >
> >
> > And yes - I see what you mean about the two characters...
> >
> > I was wrong about that one :)
> >
> >
I got it. We should write ${line.separator} as delimiter attribute value.. It
works..
Scot P. Floess-2 wrote:
>
>
> And yes - I see what you mean about the two characters...
>
> I was wrong about that one :)
>
> So, curious... I see you perform loadfile first, then fixcrlf... Is that
>
And yes - I see what you mean about the two characters...
I was wrong about that one :)
So, curious... I see you perform loadfile first, then fixcrlf... Is that
the correct order, or fixcrlf then loadfile?
On Sun, 26 Jul 2009, Raagu wrote:
No.. If we write "\r\n" , then it will take b
Again, I haven't tested this but based on the online docs for the "for"
and "foreach" I read this:
"The delimiter characters that separates the values in the "list"
attribute. Each character in the supplied string can act as a delimiter.
This follows the semantics of the StringTokenizer clas
No.. If we write "\r\n" , then it will take both 'r' and 'n' as delimiters ..
So it cant distinguish end of line..
In @{letter} I am getting whole file content..
Btw In project properties file , the output of "dir /b" will be there
That is all d directories in that directory will be there..
Not that I've tested this... But what about a \n as the delimiter? Or
maybe \r\n ???
On Sun, 26 Jul 2009, Raagu wrote:
Hello I have an ant script which reads from file "project.properties"
The code snippet is below
@{letter}
I want to read line by line. I am not getting what sh
