It was intended as a requirement: We had bugs before where newer ant versions would not work correctly with the build. They may still exist (unsure).
The simplest thing to do was to just support one single version of ant and error out otherwise, so that its completely clear. Otherwise we have to figure out a way to test all these N versions we support (else people will bring it up in release votes and users will open bug reports why XYZ doesnt build correctly on N+4 crazy version of ant). So I don't think we should remove this check (that you have the ant version we support) without infrastructure in place to test the 'additional ant versions', at least the major ones! Otherwise I really see this falling on the release manager to deal with in the future to verify and I do not think that is ok. On Fri, Oct 18, 2013 at 7:00 AM, Dawid Weiss <[email protected]> wrote: > I think the bar was "at least" 1.8+ so perhaps it's a bug in the > condition, not a requirement. > > Dawid > > On Fri, Oct 18, 2013 at 2:08 AM, Mark Miller <[email protected]> wrote: >> Anyone object to letting Ant 1.9X build releases? Is there a particular >> reason that the smoke tester looks for 1.8X specifically and does not allow >> later? >> >> I'd prefer not to downgrade if I don't have to, but I will. >> >> -- >> - Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
