You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alan Conway (JIRA)" <qp...@incubator.apache.org> on 2007/04/23 20:24:15 UTC
[jira] Updated: (QPID-450) C++ demos
[ https://issues.apache.org/jira/browse/QPID-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan Conway updated QPID-450:
-----------------------------
Fix Version/s: M2
Description:
We need some C++ demos that can be installed with the qpidc-devel documentation. They could be based on existing tests, or something a bit more imaginative.
The demos need to be properly autoconfed to build without modification in an installation of Qpid. We should be able to build, run & verify the demos automatically from an installation as a test of our installation packaging. Seems like a common enough requirement, investigate whether autotools or rpm provide support for this kind of thing.
For M2 a cleanup of the client_test and the topic test, with a bit of added commentary in the code and a demos directory and Makefile would be sufficient. Focus is on easy to read code, and minimal irrelevant complexities so Makefile should be very minimal plain-ole-make.
We should include the demos in our automated test runs, but there should be no evidence of that in the demos/ directory.
was:
We need some C++ demos that can be installed with the qpidc-devel documentation. They could be based on existing tests, or something a bit more imaginative.
The demos need to be properly autoconfed to build without modification in an installation of Qpid. We should be able to build, run & verify the demos automatically from an installation as a test of our installation packaging. Seems like a common enough requirement, investigate whether autotools or rpm provide support for this kind of thing.
> C++ demos
> ---------
>
> Key: QPID-450
> URL: https://issues.apache.org/jira/browse/QPID-450
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Client
> Reporter: Alan Conway
> Fix For: M2
>
>
> We need some C++ demos that can be installed with the qpidc-devel documentation. They could be based on existing tests, or something a bit more imaginative.
> The demos need to be properly autoconfed to build without modification in an installation of Qpid. We should be able to build, run & verify the demos automatically from an installation as a test of our installation packaging. Seems like a common enough requirement, investigate whether autotools or rpm provide support for this kind of thing.
> For M2 a cleanup of the client_test and the topic test, with a bit of added commentary in the code and a demos directory and Makefile would be sufficient. Focus is on easy to read code, and minimal irrelevant complexities so Makefile should be very minimal plain-ole-make.
> We should include the demos in our automated test runs, but there should be no evidence of that in the demos/ directory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.