|
From: Colin S. <col...@ex...> - 2003-10-21 18:18:09
|
Aside from doing something homebrew, the other choice for documentation is probably Forrest, which I've never used: http://xml.apache.org/forrest/ Alef Arendsen (JTeam) wrote: >Well, I don't really like Maven for _building_ software. For putting out >documentation though, I think it's quite nice... > >Alef > > > > >>-----Oorspronkelijk bericht----- >>Van: spr...@li... >>[mailto:spr...@li...] >> Namens Colin Sampaleanu >>Verzonden: Thursday, October 16, 2003 7:16 PM >>Aan: Rod Johnson >>CC: 'Spring Developers' >>Onderwerp: Re: [Springframework-developer] Documentation >> >> >>I actually have a lot of experience with Maven, having >>tinkered with it >>a bunch over the last year (unfortunately, the multiproject support, >>where I think Maven becomes the most useful (along with the >>docs) to me, >>is still broken in some respects (property and repository >>overrides, for >>one), but that would not have an effect on Spring. >> >>If there is consensus on this, I am willing to put in some time to >>finish this up, as necessary. >> >> >>Rod Johnson wrote: >> >> >> >>>I believe Luke Tayler did a Maven build script which works. So we >>>certainly have a starting point. >>> >>>Rod >>> >>>----- Original Message ----- >>>From: "Colin Sampaleanu" <col...@ex...> >>>To: "'Spring Developers'" >>> >>> >><spr...@li...> >> >> >>>Sent: Thursday, October 16, 2003 5:17 PM >>>Subject: Re: [Springframework-developer] Documentation >>> >>> >>> >>> >>>>From my point of view, while of course there is a general need for >>> >>> >>>>more documentation and samples, what would also be of some >>>> >>>> >>use is some >> >> >>>>general infrastructure for producing consistent and relatively >>>>professional looking docs and a website. I am not a big fan >>>> >>>> >>of Maven >> >> >>>>generated websites with nothing in them, but on the other hand, if >>>>people are willing to write documentation, Maven (and other >>>>alternatives like Forrest) make it pretty easy to put out >>>>documentation without having to worry too much about the look and >>>>feel, linking it into the site, etc. >>>> >>>>W/regards to the possibility of using Maven, one option would be to >>>>use it just for doc generation, if doing the entire build >>>> >>>> >>with it is >> >> >>>>too onerous. This approach has been used by other projects... >>>> >>>>Regards, >>>>Colin >>>> >>>>Alef Arendsen (JTeam) wrote: >>>> >>>> >>>> >>>> >>>> >>>>>Hi all, >>>>> >>>>>Since I am busy closing 2002's financial year (doing all the >>>>>accounting and stuff; I never should have started a company :), I >>>>>desperately need some things I can do when I'm totally sick of all >>>>>those numbers and spreadsheets. No internal projects here, >>>>> >>>>> >>so I was >> >> >>>>>wondering if there already is a plan for how to improve our >>>>>documentation base or if there are if there other important things >>>>>that need to be addressed. >>>>> >>>>>Juergen, other people, any thoughts? >>>>> >>>>>Thanx, >>>>> >>>>>Alef >>>>> >>>>> |