From: "Stephen Haberman" <[EMAIL PROTECTED]> > I've been working on a build.xml file and I was thinking of > incorporating exportAll/exportRef functionality. I could just do a > replace of all </?ant with </?maven-ant. But then I'd have to go in and > manually turn on the exportAll/exportRefs for each one. > > Instead of defaulting them to false, what if you default them to > maven.ant.exportAll and maven.ant.exportRefs respectively? That way I > could set the properties once and not worry about them from then on.
+1. I think thats a great idea. Users can always use <ant> instead of <maven-ant> if they prefer. > I can see how having them default on might break some existing scripts, > and perhaps maven itself, but my initial thinking is that as long as the > user turns it on in the first place, they should realize what is > happening. Though I haven't written complex inter-related Ant scripts > before, so I can't really say. References and properties are only returned by <maven-ant> to the outer build if they don't exist in the outer builds' view of the world. So it shouldn't break any exisitng scripts, be it internal Maven build scripts or end user build scripts. Plus there's the safety net of moving back to <ant> if we find any problems (which I doubt we'll find anyway). 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]>
