From: "Stephen Haberman" <[EMAIL PROTECTED]> > > 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. > > Cool, I like the idea. As long as all of the properties' defaults are > configurable, I think it's great. E.g. in your project.properties you > could set: > > maven.ant.exportAll = false > maven.ant.exportRefs = true > maven.ant.exportPrefix = mycustomprefix. > > Or even: > > maven.ant.exportPrefix = maven., torque., etc.
Though right now <maven-ant> is a task and so expects to be configured via the XML itself like other Ant tasks. <maven-ant exportRefs="true" ...> Do you think we should make <maven-ant> check for Maven properties to default the values? 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]>
