DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=40621>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=40621 Summary: Order of addXand addconfiguredX nested elements Product: Ant Version: 1.7Alpha (nightly) Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Core AssignedTo: dev@ant.apache.org ReportedBy: [EMAIL PROTECTED] Currently the ant core code calls back to the configured object in the order addX setY addConfiguredZ execute() This means that for objects that depend on the order of elements in the build file, for example filters, mappers, one cannot mix addX and addConfiguredZ. Looking at the code base, however it seems that addConfiguredZ methods are been added in to existing objects that currently have addX methods - causing potential bugs. A bug of this nature has already occured: http://issues.apache.org/bugzilla/show_bug.cgi?id=40228 (Order of mappers in chainedmapper depends on how they are defined) This was solved by adding addConfiguedX methods corresponding to the addX methods and changing IH to make addConfiguredX methods have a higer priority that addX methods - but this is a hack and is not a general solution. I propose to change the order so that it is: setY addX, addConfiguredZ (in order of the build file) execute() -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
