There is a patch already in bugzilla that adds <returns> functionality to <ant> and <antcall>.
You can indicate a particular property or a set of properties (using a prefix). Assing the value to properties with different names if needed. And you can have multiple <returns> elements. Look in bugzilla. Jose Alberto ----- Original Message ----- From: "James Strachan" <[EMAIL PROTECTED]> To: "Ant Developers List" <[EMAIL PROTECTED]> Sent: Thursday, May 23, 2002 10:44 PM Subject: Re: exporting classpath references from inner Ant builds to outer Ant builds. > From: "Erik Hatcher" <[EMAIL PROTECTED]> > > 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? > > I've patched the Ant task to have exportRefs="true|false" and > exportAll="true|false" to be the opposite of inheritRefs and inheritAll. > > For now I decided to only export (when the flag is on ;-) those references > or properties which don't already exist in the parent project. So this new > feature will never overwrite anything, only add new things not already > defined in the parent project. This seems a reasonable compromise, that its > safe, it won't change any references/properties if there is a clash. > > Seems to work pretty nicely so far; I can submit it here if anyone's > interested, it is a minor patch. Otherwise I'll submit it to Maven... > > James > > > > > _________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
