> -----Original Message----- > From: Erik Hatcher [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 23, 2002 4:07 AM > To: Ant Developers List > Subject: Re: exporting classpath references from inner Ant builds to > outer Ant builds. > > > This sounds kinda risky in that a sub-build could stomp on > properties (I > assume you'd want those exported back up too?) and references > that you did > expect to be altered. Do you envision any mechanisms for > controlling what > gets exported? All references blindly? Or some selection mechanism?
This is actually one reason why I wrote the <echoproperties> task, although if you know which properties you want to export you can use the <echo> task as well. In the sub-project, you can write the properties you care about to a file, then import those through the <property file=""> task. Since 1.5 now supports the <property refid=""> syntax, you can do this with classpaths, too (the worry issue of ';' vs. ':' imbedded in the classpath won't matter since the property will only be read back in on the same machine). -Matt Albrecht -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
