Sure, but the problem with that IMHO is that you have a static site. So what are you going to do when you find an error in the site or want to add more docs? Wait and add that in the next release coming out in 6 months? You don't want that. But crosslinking the source code is nice though. The Javadoc could be managed in Nexus and linked to there (oh, what a shameless plug!).
/Anders On Wed, Aug 15, 2012 at 11:01 PM, Manfred Moser <[email protected]> wrote: > Agreed... another benefit imho is that it is the easiest way to provide a > static website about your project for users of your artifacts. > Specifically if you are providing an API you can just host the javadoc and > potentially even the crosslinked source code right there and augement it > with further documentation and links to e.g. wiki, forums, mailing lsits > and more > > With the new fluido skin and others you can even make it look okay.. > > manfred > > On Wed, August 15, 2012 1:57 pm, Anders Hammar wrote: >> My opinion is that it is most useful for Maven plugins. It provides a >> common documentation interface that people using Maven are used to. >> >> /Anders >> >> On Wed, Aug 15, 2012 at 9:49 PM, KARR, DAVID <[email protected]> wrote: >>> I'm putting together a "Maven benefits" doc for an internal >>> organization. I was wondering if I could make any argument for the >>> value of Maven's "site generation" functionality. Our documentation is >>> on wikis, and we have a CI server that aggregates build and analysis >>> reports. Does anyone make good use of site generation when it seems >>> like it wouldn't provide any additional value? >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
