On Jul 17, 2009, at 4:15 PM, Jeff Mills wrote:
>
> Yes, I added it to the javadoc plugin's configuration element:
>
Thanks, i have added that to the pom.
Paul.
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-javadoc-plugin</artifactId>
> <executions>
> <execution>
> <goals>
> <goal>javadoc</goal>
> </goals>
> <phase>compile</phase>
> </execution>
> </execution
> <configuration>
> ...
> <doclet>com.sun.jersey.wadl.resourcedoc.ResourceDoclet</
> doclet>
>
> <docletPath>${path.separator}${project.build.outputDirectory}</
> docletPath>
> <docletArtifacts>
> ...
> </configuration>
> </plugin>
>
>
> Paul Sandoz wrote:
>>
>> Hi Jeff,
>>
>> Thanks for sending this.
>>
>> Did you add the <docletPath> to under the <configuration> element of
>> maven-javadoc-plugin plugin?
>>
>> Can you highlight where exactly you added the <docletPath> in the
>> pom.xml ?
>>
>> Paul.
>>
>> On Jul 16, 2009, at 7:50 PM, Jeff Mills wrote:
>>
>>> 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:
>>> <docletPath>${path.separator}${project.build.outputDirectory}</
>>> docletPath>
>>> 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: Re: RE: Issue with WADL "@link"
>>> Javadoc tag for dynamic content
>>> Sent from the Jersey mailing list archive at Nabble.com.
>>
>>
>>
>
> --
> View this message in context: http://n2.nabble.com/Issue-with-WADL-%22%40link%22-Javadoc-tag-for-dynamic-content-tp2807086p3275641.html
> Sent from the Jersey mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>