----- Original Message ----- From: "Stephen Haberman" <[EMAIL PROTECTED]> > > > 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.
It seems OK to me - I just didn't want to go against what Ant tasks do. AFAIK most Ant tasks don't work like this. > 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? Agreed; though already if build files swap <ant> to <maven-ant> they'll get exportRef="true" and exportAll="true" without any further hacking. > If there is a strong feeling that Ant tasks should never read > properties, that is fine. This is just my $0.02. I'm kinda sitting on the fence a bit about this, maybe erring on the side of caution I don't personally need this feature. Either stuff gets exported via <maven-ant> or folks switch to <ant> where nothing gets exported ever, or folks can use <maven-ant> and turn on/off exporting. That sounds enough for now I think. Introducing another bunch of properties might just make things even more confusing? 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]>
