[
http://jira.codehaus.org/browse/MJAVADOC-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MJAVADOC-110.
------------------------------------
Assignee: Vincent Siveton
Resolution: Fixed
Fix Version/s: 2.3
Fixed in SVN
Added your test case as IT.
> sourcepath element is not working
> ---------------------------------
>
> Key: MJAVADOC-110
> URL: http://jira.codehaus.org/browse/MJAVADOC-110
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.1, 2.2
> Reporter: Adam Lally
> Assignee: Vincent Siveton
> 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 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
