[
https://issues.apache.org/jira/browse/QPID-7265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023036#comment-16023036
]
ASF subversion and git services commented on QPID-7265:
-------------------------------------------------------
Commit 57cbe59b5a46a620553d28306b0da648a1272895 in qpid-cpp's branch
refs/heads/master from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-cpp.git;h=57cbe59 ]
QPID-7756: remove stale AMQP 0-10 JMS client content, a seperate book for that
client was based on it via QPID-7265
> migrate the AMQP 0-10 JMS client docs out of the old combined doc book.
> -----------------------------------------------------------------------
>
> Key: QPID-7265
> URL: https://issues.apache.org/jira/browse/QPID-7265
> Project: Qpid
> Issue Type: Task
> Components: Java Documentation
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: qpid-java-6.0.3
>
>
> Jakub noted that the AMQP 0-10 JMS client docs havent been udpated since
> 0.32, despite the subsequent 6.0.x 'qpid-java' releases. Keith noted that its
> because they are still part of the old 'Programming in Apache Qpid' book
> along combined with the other older client docs.
> Migrating the 0-10 client docs and consolidating them with the 0-8..0-91
> client docs the qpid-java tree is challenging as there are a lot of areas the
> two protocols differ in behaviour (which is the reason the two books exist).
> As per suggestion at \[1\], the quick and easy thing for now is to just pull
> the JMS bits out of the 'programming' guide and migrate those into the
> qpid-java tree, remainingg as a seperate book. This at least allows them to
> be published with each new release and be updated if actually needed.
> Further consolidation and improvement can be done later as desired/time
> allows.
> \[1\]
> http://mail-archives.apache.org/mod_mbox/qpid-users/201605.mbox/%3CCAFitrpQM4XO-Or822eVVCtBZtDNEM9hKSO-goqxruSksVc9EuQ%40mail.gmail.com%3E
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
