[
https://issues.apache.org/jira/browse/MJAVADOC-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17957464#comment-17957464
]
Olivier Lamy commented on MJAVADOC-110:
---------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-javadoc-plugin#505|https://github.com/apache/maven-javadoc-plugin/issues/505].
> sourcepath element is not working
> ---------------------------------
>
> Key: MJAVADOC-110
> URL: https://issues.apache.org/jira/browse/MJAVADOC-110
> Project: Maven Javadoc Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 2.1, 2.2
> Reporter: Adam Lally
> Assignee: Siveton Vincent
> Priority: Major
> Fix For: 2.3
>
> Attachments: maven-javadoc-test.zip
>
>
> The attached zip demonstrates the problem. It is a parent project that has
> one component. Just execute "mvn package" in the parent and you will get a
> File Not Found exception from the javadoc plugin.
> I've attached the javadoc plugin to the package step, and am using the
> <sourcepath> element to configure it to look in the subcomponent to get the
> source files. This works in 2.0, but fails in 2.1 and 2.2.
> (I know, I can use <aggregate> instead in this case, but I have other uses
> cases for <sourcepath> and this is just a simple example to demonstrate the
> problem.)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
