[ 
https://issues.apache.org/jira/browse/QPID-7265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15283867#comment-15283867
 ] 

Robbie Gemmell commented on QPID-7265:
--------------------------------------

 merged the changes to the 6.0.x branch now as it seems the 6.0.3 release will 
get respun, so these could then be incorporated into that rather than me 
reverting the above changes to the release scripts and adding the changes 
afterwards as I just did for 6.0.2.

https://svn.apache.org/r1743918

{noformat}
r1743918 | robbie | 2016-05-15 16:21:40 +0100 (Sun, 15 May 2016) | 4 lines

QPID-7265: merge doc changes to 6.0.x branch to add AMQP 0-10 JMS client book

Ran 'svn merge -r 1743758:1743916 ^/qpid/java/trunk/doc' in doc dir, then 
updated new pom version to match

{noformat}

I'll also update the Qpid Java release instructions 
(https://cwiki.apache.org/confluence/display/qpid/Releasing+Qpid+Java+Components)
 to account for using the tag rather than the 6.0.x branch to build the release 
content, as using the branch leads to the published docs having the wrong 
version info in them ((X+1-SNAPSHOT rather than the release version).

> 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: 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.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to