[
https://issues.apache.org/jira/browse/QPID-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115444#comment-15115444
]
ASF subversion and git services commented on QPID-6961:
-------------------------------------------------------
Commit 1726649 from [~k-wall] in branch 'java/branches/6.0.x'
[ https://svn.apache.org/r1726649 ]
QPID-6961: Use maven to generate Java Broker and (legacy) Java Client docbook
Merged from trunk with command:
svn merge -c 1722019,1722020,1722674,1722678,1722683,1722711,1725760
https://svn.apache.org/repos/asf/qpid/java/trunk
> Use maven to generate Java Broker and (legacy) Java Client docbook
> ------------------------------------------------------------------
>
> Key: QPID-6961
> URL: https://issues.apache.org/jira/browse/QPID-6961
> Project: Qpid
> Issue Type: Improvement
> Components: Documentation, Java Broker, Java Client
> Reporter: Keith Wall
> Assignee: Keith Wall
> Fix For: qpid-java-6.1
>
> Attachments:
> 0001-QPID-6961-Mechanically-translate-sources-from-DocBoo.patch
>
>
> Currently the docbook generation for the Java Broker and (legacy) JMS Client
> use Make.
> Switching it to use the docbkx-tools maven plugin will simplify the release
> process by eliminating a number of manual steps. It will remove the need to
> manually synchronise variables between the commonEntities files and the POMs.
> Also as docbkx-tools has no external dependencies (such as Doxia), it will
> mean developers on Windows PC with restricted toolset will be able to
> generate the docbooks.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
