> 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).
My thought was if something like this happens: - In build.xml, my.property is undefined - Calls subbuild.xml, my.property somehow gets defined - Back in build.xml, expecting my.property to be undefined but since we did a global replace of ant with maven-ant and set maven.ant.exportAll to true, it is now defined and breaks everything. If I'm following things correctly. It's a fairly remote case where the same properties would have to be used across build files; I agree that it shouldn't be worried about as the functionality gained is worth the risk considering the user knowingly turned on the functionality (by setting maven.ant.exportAll). - Stephen -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
