Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] Even if you're not ... was If you're going to the W3C meeting in March

From: Peter Hunsberger <peter.hunsberger@-----.--->
To: Kurt Cagle <kurt.cagle@-----.--->, Frans Englich <frans.englich@-----.--->, xml-dev@-----.---.---
Date: 2/2/2005 4:13:00 PM
On Wed, 2 Feb 2005 10:57:23 -0500, Alan Gutierrez
<alan-xml-dev@e...> wrote:

<snip>on topic XSLT in Ant discussion</snip>
> 
>  ~ Recently, I offered to provide build scripts for an XML open
>    source project. When they heard that the process would be.
> 
>        svn checkout http://foo.com/svn/foo
>        cd foo
>        ant -f mix.bootstrap.xml
>        ant
> 
>    They rejected it for the third line. And Ant script /should/
>    just work from checkout.
> 
>    But for any project of any real size, it doesn't.
> 
>    Generally, the checkout includes an endoresed ant and a pair of
>    build.sh, build.bat files that set the system class path,
>    because Ant classpath directives, for many tasks are defeated by
>    the $ANT_HOME/lib directory.

Not sure I understand all your issues here, but isn't the common way
of handling Ant script customization via proprieties files that are
read in as the first step of the Ant script?  Our scripts have no
dependencies on environment variables but do define default
proprieties that can be overridden by user proprieties files.

-- 
Peter Hunsberger


transparent
Print
Mail
Digg
delicious
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent