Description
Currently, to have Javadocs properly include Javadocs from inherited methods, we use Maven Javadocs's sourcepath and excludePackageNames settings to include source code of common libraries, that will have the inherited Javadocs and help generate links approriately.
While this works in most cases, this breaks down around release time when some libraries may have shipped and others haven't. For example, when azure-core added a dependency on azure-xml, before azure-core shipped downstream libraries were still referencing the released version. So, Javadoc had a case where azure-core source code was referenced, having Javadoc using azure-xml, but there was no dependency on azure-xml resulting in Javadoc not being able to find the azure-xml classes, failing Javadoc.
The configuration is brittle and should be reworked so that we only reference released libraries in Javadocs so downstream libraries don't begin failing Javadoc generation when a release scenario like above happens.