doclava 1.0.5 from Maven required additional dependencies

What steps will reproduce the problem?
1. Deploy the doclava 1.0.5 jar to our Maven repository, using the pom.xml from 
source.
2. Added doclet javadoc configuration.
3. Attempted build.

What is the expected output? What do you see instead?

Doclava javadoc.

What version of the product are you using? On what operating system?

doclava 1.0.5, maven-javadoc-plugin 2.8.1, maven 3.0.3

Please provide any additional information below.

I had to add a number of additional dependencies to the pom configuration for 
the javadoc plugin:

            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-javadoc-plugin</artifactId>
                <configuration>
                    <docletArtifact>
                        <groupId>com.google.doclava</groupId>
                        <artifactId>doclava</artifactId>
                        <version>1.0.5</version>
                    </docletArtifact>
                    <doclet>com.google.doclava.Doclava</doclet>
                    <bootclasspath>${sun.boot.class.path}</bootclasspath>
                    <additionalparam>
 -quiet
 -federate JDK http://download.oracle.com/javase/6/docs/api/index.html?
 -federationxml JDK http://doclava.googlecode.com/svn/static/api/openjdk-6.xml
 -hdf name "${project.name}"
 -title "${project.description} r${env.SVN_REVISION}"
 -d ${project.build.directory}/apidocs
 -hidden
 -generatesources
                    </additionalparam>
                    <useStandardDocletOptions>false</useStandardDocletOptions>
                    <additionalJOption>-J-Xmx1024m</additionalJOption>
                    <additionnalDependencies>
                        <additionnalDependency>
                            <groupId>jaxen</groupId>
                            <artifactId>jaxen</artifactId>
                            <version>1.1.1</version>
                        </additionnalDependency>
                        <additionnalDependency>
                          <groupId>com.google.jsilver</groupId>
                          <artifactId>jsilver</artifactId>
                          <version>1.0.0</version>
                        </additionnalDependency>
                        <additionnalDependency>
                            <groupId>com.google.code.guice</groupId>
                            <artifactId>guice</artifactId>
                            <version>2.0</version>                        
                        </additionnalDependency>
                        <additionnalDependency>
                            <groupId>aopalliance</groupId>
                            <artifactId>aopalliance</artifactId>
                            <version>1.0</version>                        
                        </additionnalDependency>                        
                    </additionnalDependencies>
                </configuration>
                <executions>
                    <execution>
                        <id>aggregate</id>
                        <goals>
                            <goal>aggregate</goal>
                        </goals>
                        <phase>site</phase>
                        <configuration>
                        </configuration>
                    </execution>
                </executions>
            </plugin>

Without these additionalDependencies, javadoc exited with a class not found 
exception.

I'm not entirely sure why doclava needed all these dependencies - jsilver made 
some sense.

None of these dependencies are used in our code base (we don't use AOP, jaxen 
or Guice).
Original issue reported on code.google.com by dmeibu...@gmail.com on 1 Feb 2012 at 1:22
hs10222 / doclava

doclava 1.0.5 from Maven required additional dependencies #51
