Hi Chris, Yes, I committed this fix fairly recently, because I started using 1.9.2 due to the Javadoc vulnerability fix they implemented in that version. This fix is NOT in the 2.0.3 tag. And, yes, the "antversion" could be used more effectively -- I just didn't feel like putting the time into using it right now.
So, I plan to restart the vote again in the next day or so, if I can get hold of Sandro (he is pretty busy currently also). Thank you! ~Roger Whitcomb -----Original Message----- From: Chris Bartlett [mailto:cbartlet...@gmail.com] Sent: Friday, July 19, 2013 12:52 PM To: Pivot Dev Cc: comm...@pivot.apache.org Subject: Re: svn commit: r1502657 - /pivot/trunk/build.xml I didn't see this before I mentioned coming across the same issue in my earlier email regarding the 2.0.3 release testing. http://ant.apache.org/manual/Tasks/antversion.html The Antversion task can be used for a more elegant and futureproofed solution, but this fix is fine for now. <not> <antversion atleast="1.7"/> </not> On 12 July 2013 20:10, <rwhitc...@apache.org> wrote: > Author: rwhitcomb > Date: Fri Jul 12 19:10:43 2013 > New Revision: 1502657 > > URL: http://svn.apache.org/r1502657 > Log: > Allow Ant version 1.9 also, especially now that 1.9.2 has a patch for > the Javadoc vulnerability. > > Modified: > pivot/trunk/build.xml > > Modified: pivot/trunk/build.xml > URL: > http://svn.apache.org/viewvc/pivot/trunk/build.xml?rev=1502657&r1=1502 > 656&r2=1502657&view=diff > > ====================================================================== > ======== > --- pivot/trunk/build.xml (original) > +++ pivot/trunk/build.xml Fri Jul 12 19:10:43 2013 > @@ -92,6 +92,7 @@ limitations under the License. > <or> > <contains string="${ant.version}" substring="1.7"/> > <contains string="${ant.version}" > substring="1.8"/> > + <contains string="${ant.version}" > + substring="1.9"/> > </or> > </not> > </condition> > > >