Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Tue, 16 Feb 2016 13:06:18 +0000 (UTC)
From: "Antonin Stefanutti (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12934496.1453908844000.60303.1455627978091@Atlassian.JIRA>
In-Reply-To: <JIRA.12934496.1453908844000@Atlassian.JIRA>
References: <JIRA.12934496.1453908844000@Atlassian.JIRA>
 <JIRA.12934496.1453908844780@arcas>
Subject: [jira] [Commented] (CAMEL-9541) Component docs - Maintain docs as
 part of the source code
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Antonin Stefanutti commented on CAMEL-9541:
-------------------------------------------

We should have the ability to style the description: for example code literal from the Javadoc would render as an inline code block in the description column.

Another point would be to migrate the existing examples Markdown to Asciidoc and have them included into the generated gitbook.

> Component docs - Maintain docs as part of the source code
> ---------------------------------------------------------
>
>                 Key: CAMEL-9541
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9541
>             Project: Camel
>          Issue Type: New Feature
>          Components: build system, documentation
>            Reporter: Claus Ibsen
>
> Just a ticket to capture what we are discussing at @dev
> http://camel.465427.n5.nabble.com/gitbook-based-doc-generation-td5776497.html
> We have a maven plugin that can keep all the component and endpoint options up to date.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)