Right now it's a kinda manual process. A long, long time ago, I used to
use the site goal, which generated lots of cool stuff, including the
test reports during the release. At some point it started to become too
time consuming (we also had tests randomly failing mostly due to timing,
most of them are sorted out now). Then we decided that the javadoc for
the components doesn't make a lot of sense. So we decided to only put
out camel-core and camel-spring. Then there was a discussion iirc about
the need to put the javadoc for the patch releases. As the api shouldn't
change we said that we should only put the javadoc for the minor releases.
I will put up the 2.8.0 javadoc tomorrow (or more likely during the
weekend).
Now to the question. Not sure I understand what you mean by aggregated.
For all components?
Hadrian
On 10/27/2011 12:02 PM, Daniel Kulp wrote:
Claus pointed out to me this morning that the javadoc on the website:
http://camel.apache.org/maven/current/camel-core/apidocs/
is horribly out of date (2.7.0). There aren't really instructions on the
website on how they were created and uploaded and such.
The next question is: do we want a more "aggregated and cross linked" set of
javadocs?
