On Wed, Feb 16, 2011 at 11: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. > > > > This is the same thing that Sonatype does with their Maven books for > > example. > > > > Also Hudson took that approach: [1] > > > > I think that would also be a good thing for the main OPS4J Projects. > > > > Sure, its a huge amount of work, but i think that really needs to be done > > for the Projects that we call almost "Product" status (in the OPS4J wiki > > there is also the distinction of Projects possibly raising up to Products > > when they mature). > > > > Not poking on the projects vs. product distinction here.. just maybe some > > projects need that step to benefit the user. > > > > On some other mailinglists (for example Apache Aries, who employs some > Pax > > tools in their toolchain) sometimes i read about Pax Tools are not well > > documented. I think its not necesary true in all cases, but there is a > > reason for people telling that on a mailing list. > > > > So, what i would like to ask: > > > > - Which projects do you think need major, book-reference like > documentation > > ? > > Pax-Exam, Pax-Web, Pax-Url, Pax-Logging are the one are use a lot. I > would think pax-exam is the most critical. > okay, thanks Guillaume, that exactly meets my personal impression. I think, from a users perspective today the following "entities" are most relevant: OPS4J TOOLS: Pax Runner / Pax Exam -> High Level developer tooling Possible additions: Pax Construct Probably most document critical because using them requires understanding. OPS4J BUNDLES: Pax Web + Pax Logging -> Both a service implementations Possible additions: Pax Shell & Useradmin OPS4J Foundation: Pax Tinybundles +Pax URL + (soon) Pax Repository: Foundation of the aforementioned projects. Not necessary for users but useful to understand & problem solving. Crucial when developing the projects mentioned above. > > > - What do you recommended as a technical solution. Ultimatively i would > like > > to have that in Html (online+offline) + PDF ? Also it needs to be > strongly > > versioned. > > In Karaf, we've switched our manual and main web site to a scalate > based one, hosted in svn (so easy to version, branch, etc..). > The sources are markup languages (confluence, markdown, etc...). > We're using princexml to create a pdf version. The project is a maven > project which generate the static site (with a goal to upload it) and > a war. It's also possible to run jetty to have a live updated > overview when you hack the sources. > That sounds really good. Will look at that next to the sonatype solution. If its not the same anyway. > > > Not sure, possibly it makes sense to put that all in one "Pax" book. But > the > > tooling stuff and Pax Web (a service) are quite different things. > > > > > > WDYT? > > > > Toni > > > > [1] http://www.hudson-ci.org/docs/index.html > > [2] http://gradle.org/0.9.2/docs/userguide/userguide.pdf > > > > -- > > Toni Menzel - http://www.okidokiteam.com > > > > _______________________________________________ > > general mailing list > > [email protected] > > http://lists.ops4j.org/mailman/listinfo/general > > > > > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general > -- *Toni Menzel - http://www.okidokiteam.com*
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
