> Do you think we should make <maven-ant> check for Maven properties to > default the values?
Other developers may certainly veto my opinion, but I say certainly. Default them to what the maven.ant.* properties are (either in the constructor or init or what not), but then still have it customizable on a task-by-task basis by the XML accessors. Though I'm looking at the problem strictly based on I don't want to cut and paste all of these exportRef="true"/exportAll="true" statements when really I think the behavior will be consistent on a build file-by-build file basis. E.g. all of Maven will want this functionality, so why clutter the build files? If there is a strong feeling that Ant tasks should never read properties, that is fine. This is just my $0.02. - Stephen -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
