Can you elaborate some more on your use case? Usually your using a lib, so
you know where to look for the javadoc.

2014-11-03 7:00 GMT+01:00 Jan Matèrne (jhm) <[email protected]>:

> Maintaining a 2nd pom?
> Could be the easiest ...
>
> Jan
>
> > -----Ursprüngliche Nachricht-----
> > Von: Gary Gregory [mailto:[email protected]]
> > Gesendet: Montag, 3. November 2014 02:57
> > An: Commons Developers List
> > Betreff: Master Javadoc for Commons
> >
> > Hi All:
> >
> > I think it would be nice (at least for me), if we had a master Javadoc
> > site for all of Commons in one place accessible from
> > https://commons.apache.org/
> >
> > Generating such a site from a trunks-proper checkout is easy since
> > there is a POM in that folder (mvn javadoc:aggregate).
> >
> > In order to generate a site for the latest _released_ component...
> > well, how would you do that?
> >
> > Gary
> >
> > --
> > E-Mail: [email protected] | [email protected] Java Persistence
> > with Hibernate, Second Edition <http://www.manning.com/bauer3/> JUnit
> > in Action, Second Edition <http://www.manning.com/tahchiev/>
> > Spring Batch in Action <http://www.manning.com/templier/>
> > Blog: http://garygregory.wordpress.com
> > Home: http://garygregory.com/
> > Tweet! http://twitter.com/GaryGregory
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>


-- 
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter

Reply via email to