Re: Use Maven 2 for the generation of the Cocoon documentation

2006-03-07 Thread Reinhard Poetz
Bruno Dumon wrote: OTOH, having the docs split up between a lot of little maven-sites might lessen the overview. Because of the nature of Daisy this shouldn't become a problem: - we can have one navigation document which is a collection of all block navigation docs - we have Daisy books

Re: Use Maven 2 for the generation of the Cocoon documentation

2006-03-07 Thread Ross Gardler
Bruno Dumon wrote: On Mon, 2006-03-06 at 18:39 +0100, Reinhard Poetz wrote: hepabolu wrote: Finally, adding the proposed plugin can always be added later without loosing the effort of the current setup. ok, that's right. Anyway, I can't do it myself now but if somebody is interested, I

Re: Use Maven 2 for the generation of the Cocoon documentation

2006-03-07 Thread Bruno Dumon
On Tue, 2006-03-07 at 09:06 +0100, Reinhard Poetz wrote: Bruno Dumon wrote: OTOH, having the docs split up between a lot of little maven-sites might lessen the overview. Because of the nature of Daisy this shouldn't become a problem: - we can have one navigation document which is a

Re: Use Maven 2 for the generation of the Cocoon documentation

2006-03-06 Thread Carsten Ziegeler
Reinhard Poetz schrieb: As written in my mail Status of block development (http://marc.theaimsgroup.com/?l=xml-cocoon-devm=114165989221631w=2) I propose a change in the Cocoon documentation creation: We have put a lot of work into the Mavenization of the Cocoon build system. As you

Re: Use Maven 2 for the generation of the Cocoon documentation

2006-03-06 Thread Reinhard Poetz
Carsten Ziegeler wrote: Reinhard Poetz schrieb: As written in my mail Status of block development (http://marc.theaimsgroup.com/?l=xml-cocoon-devm=114165989221631w=2) I propose a change in the Cocoon documentation creation: We have put a lot of work into the Mavenization of the Cocoon build

Re: Use Maven 2 for the generation of the Cocoon documentation

2006-03-06 Thread hepabolu
Carsten Ziegeler said the following on 06-03-2006 17:49: I'm more than +1 for getting the reports Maven provides for us on our website. I'm not sure if we need a plugin for the daisy docs or if just linking from the maven generated site is enough. Whatever works best. Let's do this one step at

Re: Use Maven 2 for the generation of the Cocoon documentation

2006-03-06 Thread Reinhard Poetz
hepabolu wrote: Finally, adding the proposed plugin can always be added later without loosing the effort of the current setup. ok, that's right. Anyway, I can't do it myself now but if somebody is interested, I can help. Maybe some of the Daisy gurus here can comment on the idea itself?

Re: Use Maven 2 for the generation of the Cocoon documentation

2006-03-06 Thread Carsten Ziegeler
hepabolu schrieb: Carsten Ziegeler said the following on 06-03-2006 17:49: I'm more than +1 for getting the reports Maven provides for us on our website. I'm not sure if we need a plugin for the daisy docs or if just linking from the maven generated site is enough. Whatever works best.

Re: Use Maven 2 for the generation of the Cocoon documentation

2006-03-06 Thread Ross Gardler
Reinhard Poetz wrote: As written in my mail Status of block development (http://marc.theaimsgroup.com/?l=xml-cocoon-devm=114165989221631w=2) I propose a change in the Cocoon documentation creation: We have put a lot of work into the Mavenization of the Cocoon build system. As you might

Re: Use Maven 2 for the generation of the Cocoon documentation

2006-03-06 Thread Bruno Dumon
On Mon, 2006-03-06 at 18:39 +0100, Reinhard Poetz wrote: hepabolu wrote: Finally, adding the proposed plugin can always be added later without loosing the effort of the current setup. ok, that's right. Anyway, I can't do it myself now but if somebody is interested, I can help. Maybe