Hi all, we currently build an aggregate JavaDoc API for the UIMA Java SDK that includes documentation for all modules. Due to a change in the JavaDoc Maven Plugin that happened a while back, this has become a bit of a pain. In particular, we seem to have to to manually explicitly include all the dependencies of the modules for which the documentation is build as "additionalDependencies" in the configuration of the JavaDoc plugin - they are not picked up automatically. IMHO this is rather annoying. In fact, I am considering to not build the aggregate JavaDoc anymore and just build JavaDoc per-module.
Any opinions on that? Or maybe somebody knows how to use the JavaDoc plugin in aggregate mode without having to explicitly define these extra dependencies? Cheers, -- Richard
