qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wall (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-6961) Use maven to generate Java Broker and (legacy) Java Client docbook
Date Mon, 11 Jan 2016 08:54:39 GMT

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

Keith Wall commented on QPID-6961:

Yes, we should merge to 6.0.x.

> 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

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message