From: "Stephen Haberman" <[EMAIL PROTECTED]> > > 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.
Maybe just to be totally safe we could add an extra prefix, like "maven." so that only properties/references starting with a certain prefix are exported; then so long as noone uses a "maven.property" in their own build file then it could never create a new property that your outer build didn't expect. (We could even make <maven-ant> default this filter prefix to 'maven.' since its primarily focussed on exporting Maven's properties/references. 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]>
