Also, on jar projects, where javadoc does work, when included as a site report, it creates the javadocs, but doesn't correctly create the index.html page, so there is no javadocs on that page.
-Stephen On 10/20/05, Stephen Duncan <[EMAIL PROTECTED]> wrote: > Anybody have any more information on this? Taking away a feature > without any explanation is a little frustrating... > > -Stephen > > On 10/19/05, John Mendonca <[EMAIL PROTECTED]> wrote: > > After this new version of maven 2, I can no longer create javadocs for > > my war packaged projects, as they are not 'classpath-capable' packages. > > This does make sense somewhat, I am not making libraries for people to > > use, so why should I need javadocs? These docs are not for users of my > > code, but rather my team members who will sometime need to understand > > and maintain my code. Perhaps there is a configuration option for the > > javadoc plugin I do not know of that can turn off this functionality? > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Stephen Duncan Jr > www.stephenduncanjr.com > -- Stephen Duncan Jr www.stephenduncanjr.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
