[
https://issues.apache.org/jira/browse/QPID-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091303#comment-15091303
]
Alex Rudyy commented on QPID-6961:
----------------------------------
The changes look good to me. We might want to port them into 6.0.x branch in
order to be able to generate 6.0.x releases in the same way. Otherwise, we
would need to restore the code in qpid/site/scripts/gen-java-release-books to
be able to generate the 6.0.x docbooks in old way. The question is whether we
want to move docbook sources into the corresponding java modules before the
merge?
> 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: Alex Rudyy
> 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
