[ http://jira.codehaus.org/browse/MJAVADOC-61?page=all ]
Vincent Siveton closed MJAVADOC-61.
-----------------------------------
Assignee: Vincent Siveton
Resolution: Fixed
Fix Version/s: 2.1
Used executedProject.getCompileSourceRoots() instead of
project.getCompileSourceRoots() to return the source paths.
NB: if your code generator is a maven plugin, it should handle the
compileSourceRoots ie:
project.addCompileSourceRoot( outputDirectory );
> Adding custom source paths to javadoc
> -------------------------------------
>
> Key: MJAVADOC-61
> URL: http://jira.codehaus.org/browse/MJAVADOC-61
> Project: Maven 2.x Javadoc Plugin
> Issue Type: New Feature
> Affects Versions: 2.0-beta-3
> Environment: FedoreCore 4 kernel 2.6.10-1.760_FC3smp #1
> Reporter: Erik van Zijst
> Assigned To: Vincent Siveton
> Fix For: 2.1
>
>
> I have a code generator that creates sources during the compile stage. These
> sources end up in a custom directory
> (${project.build.directory}/generated-sources/main/java). The problem is that
> javadoc skips these files when it generates the documentation. What I'm
> looking for is a way to manipulate javadoc's sourcefilenames argument.
> I have already tried adding
> <sourceRoot>${project.build.directory}/generated-sources/main/java</sourceRoot>
> to the code generation step, but it didn't affect javadoc.
--
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
