[jira] Created: (MJAVADOC-195) javadoc generation on @Test(expected...) throws Exception (aggregation issue)

javadoc generation on @Test(expected...) throws Exception (aggregation issue)
-----------------------------------------------------------------------------

                 Key: MJAVADOC-195
                 URL: http://jira.codehaus.org/browse/MJAVADOC-195
             Project: Maven 2.x Javadoc Plugin
          Issue Type: Bug
    Affects Versions: 2.3
         Environment: 1.5.x
            Reporter: Quinten Verheyen


In a recent build of ours, running javadoc:javadoc on our modules gave the following exception :

[INFO] An error has occurred in JavaDocs report generation:Exit code: 1 - javadoc: error - In doclet class com.sun.tools.doclets.standard.Standard,  method start has thrown an exception java.lang.reflect.InvocationTargetException
java.lang.AssertionError: cannot find method org.junit.Test.expected()
        at com.sun.tools.javac.jvm.ClassReader$AnnotationDeproxy.findAccessMethod(ClassReader.java:1074)

It took me some time to find out that this ONLY fails when the test is part of a module which is more then 1 level deeper then the module from wich the javadoc command is being run.

To illustrate, the usage of @Test(expected=...) occured in several of our modules, one of them was directly below the root and a couple of others an extra level down. When I temporarily commented out the modules who were an extra level down, the javadoc generation succeeded, despite that fact there were still tests using @Test(expected=...).

Below the configuration in our root pom.xml :

<plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-javadoc-plugin</artifactId>
                <version>2.3</version>
                <configuration>
                    <aggregate>true</aggregate>
                    <links>
                        <link>http://java.sun.com/j2se/1.5.0/docs/api</link>
                        <link>http://static.springframework.org/spring/docs/2.0.x/api</link>
                    </links>
                </configuration>
            </plugin>

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ http://jira.codehaus.org/browse/MJAVADOC-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137375#action_137375 ]

Vincent Siveton commented on MJAVADOC-195:
------------------------------------------

Could you test it with 2.4 and 2.5-SNAPSHOT?
Also, could send us a test case?

> javadoc generation on @Test(expected...) throws Exception (aggregation issue)
> -----------------------------------------------------------------------------
>
>                 Key: MJAVADOC-195
>                 URL: http://jira.codehaus.org/browse/MJAVADOC-195
>             Project: Maven 2.x Javadoc Plugin
>          Issue Type: Bug
>    Affects Versions: 2.3
>         Environment: 1.5.x
>            Reporter: Quinten Verheyen
>
> In a recent build of ours, running javadoc:javadoc on our modules gave the following exception :
> [INFO] An error has occurred in JavaDocs report generation:Exit code: 1 - javadoc: error - In doclet class com.sun.tools.doclets.standard.Standard,  method start has thrown an exception java.lang.reflect.InvocationTargetException
> java.lang.AssertionError: cannot find method org.junit.Test.expected()
>         at com.sun.tools.javac.jvm.ClassReader$AnnotationDeproxy.findAccessMethod(ClassReader.java:1074)
> It took me some time to find out that this ONLY fails when the test is part of a module which is more then 1 level deeper then the module from wich the javadoc command is being run.
> To illustrate, the usage of @Test(expected=...) occured in several of our modules, one of them was directly below the root and a couple of others an extra level down. When I temporarily commented out the modules who were an extra level down, the javadoc generation succeeded, despite that fact there were still tests using @Test(expected=...).
> Below the configuration in our root pom.xml :
> <plugin>
>                 <groupId>org.apache.maven.plugins</groupId>
>                 <artifactId>maven-javadoc-plugin</artifactId>
>                 <version>2.3</version>
>                 <configuration>
>                     <aggregate>true</aggregate>
>                     <links>
>                         <link>http://java.sun.com/j2se/1.5.0/docs/api</link>
>                         <link>http://static.springframework.org/spring/docs/2.0.x/api</link>
>                     </links>
>                 </configuration>
>             </plugin>

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ http://jira.codehaus.org/browse/MJAVADOC-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vincent Siveton closed MJAVADOC-195.
------------------------------------

    Resolution: Cannot Reproduce

Without any feedbacks, we can't help you.
BTW, 2.5-snapshot should fix your use case with javadoc:aggregate goal

> javadoc generation on @Test(expected...) throws Exception (aggregation issue)
> -----------------------------------------------------------------------------
>
>                 Key: MJAVADOC-195
>                 URL: http://jira.codehaus.org/browse/MJAVADOC-195
>             Project: Maven 2.x Javadoc Plugin
>          Issue Type: Bug
>    Affects Versions: 2.3
>         Environment: 1.5.x
>            Reporter: Quinten Verheyen
>
> In a recent build of ours, running javadoc:javadoc on our modules gave the following exception :
> [INFO] An error has occurred in JavaDocs report generation:Exit code: 1 - javadoc: error - In doclet class com.sun.tools.doclets.standard.Standard,  method start has thrown an exception java.lang.reflect.InvocationTargetException
> java.lang.AssertionError: cannot find method org.junit.Test.expected()
>         at com.sun.tools.javac.jvm.ClassReader$AnnotationDeproxy.findAccessMethod(ClassReader.java:1074)
> It took me some time to find out that this ONLY fails when the test is part of a module which is more then 1 level deeper then the module from wich the javadoc command is being run.
> To illustrate, the usage of @Test(expected=...) occured in several of our modules, one of them was directly below the root and a couple of others an extra level down. When I temporarily commented out the modules who were an extra level down, the javadoc generation succeeded, despite that fact there were still tests using @Test(expected=...).
> Below the configuration in our root pom.xml :
> <plugin>
>                 <groupId>org.apache.maven.plugins</groupId>
>                 <artifactId>maven-javadoc-plugin</artifactId>
>                 <version>2.3</version>
>                 <configuration>
>                     <aggregate>true</aggregate>
>                     <links>
>                         <link>http://java.sun.com/j2se/1.5.0/docs/api</link>
>                         <link>http://static.springframework.org/spring/docs/2.0.x/api</link>
>                     </links>
>                 </configuration>
>             </plugin>

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ http://jira.codehaus.org/browse/MJAVADOC-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197583#action_197583 ]

Richard Ziegler commented on MJAVADOC-195:
------------------------------------------

This affects 2.5 and 2.6 too

> javadoc generation on @Test(expected...) throws Exception (aggregation issue)
> -----------------------------------------------------------------------------
>
>                 Key: MJAVADOC-195
>                 URL: http://jira.codehaus.org/browse/MJAVADOC-195
>             Project: Maven 2.x Javadoc Plugin
>          Issue Type: Bug
>    Affects Versions: 2.3
>         Environment: 1.5.x
>            Reporter: Quinten Verheyen
>
> In a recent build of ours, running javadoc:javadoc on our modules gave the following exception :
> [INFO] An error has occurred in JavaDocs report generation:Exit code: 1 - javadoc: error - In doclet class com.sun.tools.doclets.standard.Standard,  method start has thrown an exception java.lang.reflect.InvocationTargetException
> java.lang.AssertionError: cannot find method org.junit.Test.expected()
>         at com.sun.tools.javac.jvm.ClassReader$AnnotationDeproxy.findAccessMethod(ClassReader.java:1074)
> It took me some time to find out that this ONLY fails when the test is part of a module which is more then 1 level deeper then the module from wich the javadoc command is being run.
> To illustrate, the usage of @Test(expected=...) occured in several of our modules, one of them was directly below the root and a couple of others an extra level down. When I temporarily commented out the modules who were an extra level down, the javadoc generation succeeded, despite that fact there were still tests using @Test(expected=...).
> Below the configuration in our root pom.xml :
> <plugin>
>                 <groupId>org.apache.maven.plugins</groupId>
>                 <artifactId>maven-javadoc-plugin</artifactId>
>                 <version>2.3</version>
>                 <configuration>
>                     <aggregate>true</aggregate>
>                     <links>
>                         <link>http://java.sun.com/j2se/1.5.0/docs/api</link>
>                         <link>http://static.springframework.org/spring/docs/2.0.x/api</link>
>                     </links>
>                 </configuration>
>             </plugin>

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira