[
https://issues.apache.org/jira/browse/MJAVADOC-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17957435#comment-17957435
]
Olivier Lamy commented on MJAVADOC-39:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-javadoc-plugin#486|https://github.com/apache/maven-javadoc-plugin/issues/486].
> javadoc plugin (beta 3) chdir in 'target/site/apidocs', causing <overview>
> parameter to fail
> --------------------------------------------------------------------------------------------
>
> Key: MJAVADOC-39
> URL: https://issues.apache.org/jira/browse/MJAVADOC-39
> Project: Maven Javadoc Plugin (Moved to GitHub Issues)
> Issue 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
> Priority: Major
>
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
