Jonathan Robie wrote:
On 03/30/2010 03:20 PM, Rafael Schloming wrote:
I'm +1 on the -1 on maven. We've had many bad experiences with maven
in the past. It's basically impossible to produce repeatable builds
with maven for many well documented reasons that I won't recount.
In general I would prefer to avoid adding more build technologies into
the mix for qpid unless it is *absolutely* necessary. We already have
ant, nant, autotools, cmake, make, rake, distutils, and various shell
scripts already required to actually produce something useful from our
source code. Let's not make this picture any worse.
I imagine using xmllint for xinclude is the bit that doesn't work on
Windows.
The Saxon + FOP approach works well on Windows, I'd probably support
that with an ant file that downloads everything it needs into
subdirectories if not present.
Any objections to that approach?
I think that's fine as long as the build is capable of using locally
installed tools as well, and the download option is provided as a
separate convenience.
In general formal build environments won't allow arbitrary access to the
internet when building pristine versions of things, so it would be
problematic if the build system required this.
--Rafael
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
