On 08/22/2011 11:16 AM, Keith Wall wrote:
On 18 August 2011 16:14, Gordon Sim<[email protected]> wrote:
On 08/18/2011 04:09 PM, Robbie Gemmell wrote:
The rationale for the change was to add an extension point to the
build system to enable client modules, such as transports and
authentication/authorisation add-ons. The easiest way of doing this
was the property used which has happened to involve requiring a 3 year
old version of Ant.
Should it be a policy to support things that are over 6 years old at
this point? RHEL4? I've been seeing RHEL5 based builds getting broken
with increasing regularity recently...
I'm not suggesting it should be policy. All I was asking was for
clarification and context on the change in question to help inform any
possible proposals on alternatives.
While we shouldn't have to contort ourselves to workaround the lack of well
established features, if there are simple alternatives that are less
exclusive that is surely a reasonable thing to consider.
I commited a change under QPID-3365 to avoid the dependency on Ant 1.7.1.
The build should now be working under Ant 1.6.x once again.
Thanks!
(I'll stress again that I am not by any means suggesting there should be
a policy to support older versions. However I very much appreciate the
gesture here).
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
