[ http://jira.codehaus.org/browse/MJAVADOC-39?page=all ]
     
Mike Perham closed MJAVADOC-39:
-------------------------------

     Assign To: Mike Perham
    Resolution: Fixed

I believe this is fixed by MJAVADOC-19.

> javadoc plugin (beta 3) chdir in 'target/site/apidocs', causing <overview> 
> parameter to fail
> --------------------------------------------------------------------------------------------
>
>          Key: MJAVADOC-39
>          URL: http://jira.codehaus.org/browse/MJAVADOC-39
>      Project: Maven 2.x Javadoc Plugin
>         Type: Bug

>  Environment: Maven 2.0.1
> maven-javadoc-plugin/2.0-beta-3
> Java 1.5.0 update 6
> Windows XP (French)
>     Reporter: Martin Desruisseaux
>     Assignee: Mike Perham

>
>
> When executed with "mvn site", the javadoc tool seems to be executed from the 
> "target/site/apidocs" directory. I tested and verified that the following 
> parameter:
>     <overview>
>         overview.html
>     </overview>
> search for an overview file in the "target/site/apidocs" directory, not in 
> the directory that contains the pom.xml file as I would have expected. Since 
> this directory is not supposed to exists before the javadoc plugin is 
> executed, it is hard to put an overview file there...
> I also verified that the following parameter:
>     <overview>
>         ${project.build.sourceDirectory}/overview.html
>     </overview>
> search for an overview file in a non-existent directory, since 
> "target/site/apidocs" is the parent directory.
> As a side note, I also noticed that "mvn javadoc:javadoc" creates a quite 
> different directory structure, with an almost empty "apidocs" directory and 
> an unused "images" directory.

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to