To add something to the first issue. This is solved in subversion. If you check out the plugin and build it, you should get a javadoc plugin that doesn't show you an empty page, but shows the javadoc index page.
Jos On 11/18/05, Anuerin Diaz <[EMAIL PROTECTED]> wrote: > i just browsed JIRA and the second issue is the same as the one in > http://jira.codehaus.org/browse/MNG-1572. i will attach my scenario on > that issue if it would help in detecting the real cause. > > ciao! > > On 11/18/05, Anuerin Diaz <[EMAIL PROTECTED]> wrote: > > hi, > > > > i have a a couple of issues with using the javadoc plugin. i am > > looking forward to a similar result like the one found in > > http://qdox.codehaus.org/maven-reports.html where multiple reports are > > attached in the generated site. i have attached the maven-javadoc > > plugin in the reporting elements of my pom file and the plugin is > > being called during site generation, however: > > > > the target/apidoc/index.html is always renders an empty page (but > > not an empty file). the generation was successful because i can the > > actual javadocs for each module class and the other files in the > > apidoc directory seems to contain the correct entries (e.g. > > index-all.html, overview-*.html) and could navigate to the actual > > class javadoc from there. > > > > my html skills are virtually nonexistent but i think the most > > pertinent part of the index.html page is the part i quoted below. the > > other parts of the html page seems to be rendered perfectly (sidebars, > > footers, etc.) > > =================== > > <div id="bodyColumn"> > > <div id="contentBox"></div> > > </div> > > > > <div class="clear"> > > <hr /> > > </div> > > =================== > > > > > > my second issue with the javadoc plugin when it is used together > > with the clover plugin. the javadoc plugin is causing the > > clover-plugin to fail. used on its own the clover plugin works fine > > but if i declare the javadoc and clover plugins at the same time then > > the clover plugin will fail with a "Can't find bundle for base name > > clover-report, locale fi_FI". changing the regional settings of my > > workstation to en_US provides a temporary solution but not something > > that management will endorse. as far as i can see the clover plugin > > does not have a configuration setting for locale, and i am still > > confused why this problem will only surface if the javadoc plugin is > > also activated. > > > > my third issue with the javadoc was only found when i tried setting > > the locale attribute to "en_US" to fix my second issue. javadoc > > execution will always fail with a "Embedded error: Exit code: 1 - > > javadoc: option -locale must be first on the command line." message > > even though it is the only configuration item for the javadoc plugin > > on my pom. > > > > am i doing using these plugins incorrectly? thanks. > > > > ciao! > > > > -- > > > > "Programming, an artform that fights back" > > > > Anuerin G. Diaz > > Registered Linux User #246176 > > Friendly Linux Board @ http://mandrivausers.org/index.php > > http://capsule.ramfree17.org , when you absolutely have nothing else > > better to do > > > > > -- > > "Programming, an artform that fights back" > > Anuerin G. Diaz > Registered Linux User #246176 > Friendly Linux Board @ http://mandrivausers.org/index.php > http://capsule.ramfree17.org , when you absolutely have nothing else > better to do > > --------------------------------------------------------------------- > 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]
