Is there a workaround for maven-javadoc-plugin bug MJAVADOC-414?

While using maven-javadoc-plugin to generate test Javadoc I suddenly got multiple errors stating that the Javadoc plugin was unable to find any classes from my main codebase. While running the test-javadoc goal the classpath contained only classes within the src/test folder; no classes from src/main were visible to the plugin. This bug occurs on maven-javadoc-plugin versions 2.10, 2.10.1 and 2.10.2. This error is the officially recognized bug MJAVADOC-414, and you can view the bug report here. The official bug report lists a workaround that involves downgrading the plugin to version 2.9.1, which I have confirmed is a successful workaround for the errors. It is also worth noting that the bug is currently listed as fixed, and should be eliminated upon the next release of maven-javadoc-plugin, which is likely version 2.11. However, I am trying to find a workaround to MJAVADOC-414 that does not involve the overkill of downgrading 3 release versions. Does anyone know of a workaround that will successfully eliminate the erroneous error messages about missing class references in an alternative way that doesn't involve downgrading?