I also use docbook for this task, similar to Apache ds, but scalate is also fine for me...
I am also of the opinion that pax runner and pax exam are the most critical to describe. but I am not sure if we should create one book or one per project. both ways have their pros and cons. on one hand there is version on the other e.g. that runner and exam eg have much in common; well, one depends on the other.... but the greater the distance between code and docs the higher the probability that they drift apart. in addition we should not forget that sonatype eg pays ppl for writing those books, we do not have those capacities... ok but still in think it is worth a try.. in addition I think it's best to keep the number of books down and have one for exam, runner,... and one for logging, web; maybe an own for wicket? my 2 cents kind regards Andreas On Feb 16, 2011 12:41 PM, "Pete Carapetyan" <[email protected]> wrote: > I had promised to help in this effort as well, and collected many notes on > how I made my pax projects work as the primary templates for my modules, but > have yet to do anything with my notes. > > Will monitor this thread and look for the right time. I've got about 14 > modules written and running and I'm still learning new tricks, so I keep > thinking if I just wait a little longer things will "settle down". So much > to learn... > > On Wed, Feb 16, 2011 at 4:38 AM, Guillaume Nodet <[email protected]> wrote: > >> On Wed, Feb 16, 2011 at 10:54, Toni Menzel <[email protected]> wrote: >> > Gang, >> > >> > Reading the Gradle Userguide PDF offline while being on the ride [2] it >> > stuck to me: I felt very comfy & home when knowing there is a PDF on my >> disk >> > that covers all i need for a OSS tool to work start with. >>
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
