+++1 for me On Thu, Apr 2, 2009 at 3:19 PM, Jean-Baptiste Onofré <[email protected]>wrote:
> Hi Charles, > > Yes, it's exactly the same as in Camel. > > In Camel, the user manual is store in the project itself (in the > tooling/camel-manual subproject), in the DocBook format, and it uses DocBk > to generate output (PDF/HTML). > > I propose to do exactly the same in SMX. > > The main purpose is : > - to have a documentation already up to date at the build time > - store the documentation in a central project > - be able to generate more "professional" look and format > > Regards > JB > > > Charles Moulliard wrote: > >> Jean-Baptiste, >> >> If the strategy proposed is the same as used to generate Apache Camel >> documentation, I agree. Otherwise, it makes no sense to reinvent the >> wheel. >> >> Regards, >> >> Charles >> >> On Thu, Apr 2, 2009 at 2:56 PM, Jean-Baptiste Onofré <[email protected] >> >wrote: >> >> Hi (again :)), >>> >>> As already discussed on the user mailing list, I propose to create a >>> documentation project. >>> >>> This project is a maven one : >>> - inherit the SMX super POM >>> - define pom.xml >>> - etc >>> >>> It stores DocBook resources. >>> >>> The purpose is to generate (within each SMX continuous integration build) >>> an up to date documentation into several formats : PDF, HTML, etc. >>> >>> It can use Maven Doxia or Google Docbk plugin to generate it into a build >>> phase (package for example). >>> >>> What do you think ? >>> >>> Regards >>> JB >>> >>> >>
