On Sun, 2009-12-13 at 22:00 +0000, Cliff Jansen (Interop Systems Inc)
wrote:
> I have taken a first stab at providing the release artifact for
> WCF. (QPID-2267)
>
> Like the python and ruby cases, it consists of a static snapshot of
> the relevant subdirectory.
>
> Unlike those cases, it cannot be built by the user unless the C++
> artifact is also downloaded and built to provide the necessary
> qpidclient.dll, qpidcommon.dll, and C++ include files. As an
> alternative, the artifact could include both the wcf subtree and the
> qpid-cpp-{VER} contents in one place. However, I see little benefit
> of doing so compared to downloading each separately.
I think that is the best wqe are going to do for 0.6, however all of the
other artifacts are standalone afaik. I don't mean to say that they
can't benefit from having other parts of the tree there (for example the
python system tests in the python tree are useful to both C++ and Java I
think.
So I do think that for 0.7 we need to produce a single way (script or
makefile or something) which allows you to produce something useful in
the WCF context given a tree containing the WCF code and however much of
the C++ code it needs - probably starting with all of it for ease.
The point here is that the artifacts be useful in and of themselves.
Andrew
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
