That would pretty much be perfect.  Tho I cant see why all stripped lines being 
completely removed isnt desirable all the time.

As a side note It also leaves comments.  If you comment private conf 
dependencys/confs etc they get left in.  However I think its pretty much 
impossible to programmatically work out if a comment should remain or not so 
they are all best left in.

Would the making of this stripping or the 'pretty-print' attribute make it into 
rc2?  Or is it too late?  Its quite deirable for our enterprise ivyrep solution.

Many thanks,


Alex Foreman
Morgan Stanley | Technology
20 Cabot Square | Canary Wharf | Floor 06
London, E14 4QW
Phone: +44 20 7677-5732
[EMAIL PROTECTED]

-----Original Message-----
From: Maarten Coene [mailto:[EMAIL PROTECTED]
Sent: 29 October 2008 20:08
To: [email protected]
Subject: Re: Stripped lines in ivy.xml

You could do a reformat with XSLT on the delivered ivy file.
But maybe we can add a "pretty-print" attribute on the deliver task to do that 
automatically for you?

Maarten



----- Original Message ----
From: "Foreman, Alex (IT)" <[EMAIL PROTECTED]>
To: [email protected]
Sent: Wednesday, October 29, 2008 7:05:51 PM
Subject: Stripped lines in ivy.xml

Take for instance this delivered ivy xml

        <configurations>
                <conf name="build-main" extends="runtime"/>



                <conf name="runtime"/>

        </configurations>

There were two other confs inbetween them and one below which have been 
stripped but left white space.

Can these empty lines be completely removed so it turns into:
        <configurations>
                <conf name="build-main" extends="runtime"/>
                <conf name="runtime"/>
        </configurations>

Without any human intervention?

Thanks,

Alex Foreman
Morgan Stanley | Technology
20 Cabot Square | Canary Wharf | Floor 06 London, E14 4QW
Phone: +44 20 7677-5732
[EMAIL PROTECTED]
--------------------------------------------------------

NOTICE: If received in error, please destroy and notify sender. Sender does not 
intend to waive confidentiality or privilege. Use of this email is prohibited 
when received in error.
--------------------------------------------------------

NOTICE: If received in error, please destroy and notify sender. Sender does not 
intend to waive confidentiality or privilege. Use of this email is prohibited 
when received in error.

Reply via email to