You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (JIRA)" <ji...@apache.org> on 2016/02/11 15:19:18 UTC
[jira] [Assigned] (QPID-6961) Use maven to generate Java Broker and
(legacy) Java Client docbook
[ https://issues.apache.org/jira/browse/QPID-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy reassigned QPID-6961:
--------------------------------
Assignee: Keith Wall (was: Alex Rudyy)
Keith,
Please review the changes
> 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org