Yeah, that works:

I just used the lf ascii code and that works:

     <replaceregexp
            match="(?&lt;=&lt;\/method&gt;)\s*(?=^[\t ]*&lt;method)"
            replace="&#10;&#10;"
            flags="gmi"
            encoding="UTF-8"
    >
            <fileset dir="." includes="${xml.include}" />
    </replaceregexp >

On 7/18/06, Aaron Davies <[EMAIL PROTECTED]> wrote:

Oops, that should of course be &lf;.

On 7/18/06, Aaron Davies <[EMAIL PROTECTED]> wrote:
> How about using entities? Are &#10; or &#xA; or &#lf; defined in the
> XML dialect we're using?
>
> On 7/18/06, Stefano Marsili <[EMAIL PROTECTED]> wrote:
> > I strongly doubt it's the easiest way to achieve what
> > you want, but you could write a script or define a
> > scriptdef that writes the \n (0x0A) to a property and
> > use it. Anyway, if you want your build to be platform
> > indipendent, I think ${line.separator} is still the
> > best choice.
> >
> > Stefano Marsili
> > PFunctions: http://www.efanomars.net/pf
> >
> > --- Alex Egg <[EMAIL PROTECTED]> wrote:
> >
> > > Hi,
> > >
> > > I think some of your message got cut off... Is there
> > > any way you can think
> > > of to specify the line break literally in the xml
> > > attribute?
> > >
> > > (Using the line.separator property works by the
> > > way!)
> > >
> > > Thanks,
> > > Alex
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam?  Yahoo! Mail has the best spam protection around
> > http://mail.yahoo.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> Aaron Davies
> [EMAIL PROTECTED]
>


--
Aaron Davies
[EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to