Until the maven site plugin is capable of actually producing a testable multi-module website, I’m putting all efforts on hold to include any docs (and JavaDocs in particular) into the Wicket distribution. I’m fed up with spending my free time figuring out the magical incantation to generate a site that runs in my browser without having to deploy it to a remote location. See MSITE-366 for my test case project that just won’t work. If you are desperate to get them javadocs, vote for that issue. Until then: you’re SOL.
when are people going to realize that maven is a pile of dog poopy?
when are people going to realize that Maven is here to stay and gets better with every release. For all its warts it actually works decently on my projects. What I showed here is just a bug like in any other project.
[...] threw this video together as a response to Martjin Dashorst’s post on why Javadoc isn’t distributed with Wicket. Given the ease with which you can browse Javadoc in m2eclipse, I think the days of cutting a [...]
Martjin, I spent some hours thinking about this issue today. Here’s my response:
http://blogs.sonatype.com/people/book/2008/10/23/browsing-javadoc-for-dependencies-in-eclipse-m2eclipse/
Yeah, I’m going crazy about this maven site-plugin site/staging/deploy crap, too. Way we do it is by just running “site” and copying the module site directly into the parent pom’s site. Seems to work fine from there.