deltaspike-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Porter <lightguard...@gmail.com>
Subject Re: [jira] [Created] (DELTASPIKE-13) Choose documentation format and tools
Date Thu, 15 Dec 2011 23:25:22 GMT
-1 to DocBook it's difficult to get people up to speed and is a turn off
for new contributors.

Also what exactly do you mean by "buildable with maven"? Does that mean we
need a plugin? Can an ant task or other scripting work?

On Thu, Dec 15, 2011 at 15:39, Shane Bryzak (Created) (JIRA) <
jira@apache.org> wrote:

> Choose documentation format and tools
> -------------------------------------
>
>                 Key: DELTASPIKE-13
>                 URL: https://issues.apache.org/jira/browse/DELTASPIKE-13
>             Project: DeltaSpike
>          Issue Type: Task
>            Reporter: Shane Bryzak
>            Assignee: Gerhard Petracek
>
>
> We need to decide on a documentation format for the DeltaSpike
> documentation.  Requirements are:
>
> 1. Kept in the VCS with the DeltaSpike codebase
> 2. Buildable with Maven
> 3. Can generate multiple formats, including HTML and PDF
>
> Currently the "industry standard" is DocBook, however there may be other
> alternatives which are more suitable.  Suggestions welcome here.
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> administrators:
> https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>


-- 
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp

Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling

PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message