I had this problem, too, with Maven 2.0.9 on Windows XP. It seems that the
problem is that the example classes are not in the docletpath. I tried
adding ${project.build.outputDirectory} to the extdirs and bootclasspath
options to no avail. However, adding it to the docletPath solved the
problem. The javadoc plugin builds the docletpath parameter to javadoc from
the docletArtifacts then appends the docletPath plugin option. Note that it
does not add a path separator when appending so you have to include that in
the docletPath:
${path.separator}${project.build.outputDirectory}
Paul Sandoz wrote:
>
> Hi David,
>
> I cannot explain why the maven-javadoc-plugin is not including the
> compiled application classes in the class path.
>
> Perhaps it is a windows thing? Naresh do you have a windows box to
> verify if this works for you?
>
> Paul.
>
> On May 7, 2009, at 8:08 PM, Woodbury David-R28558 wrote:
>
>> Hi Paul:
>>
>> Yes, similar issue with Maven 2.0.9. The generated sources all seem
>> to be there and they do get built.
>>
>> David
>>
>
>
--
View this message in context: http://n2.nabble.com/Issue-with-WADL-%22%40link%22-Javadoc-tag-for-dynamic-content-tp2807086p3268828.html
Sent from the Jersey mailing list archive at Nabble.com.