[
https://issues.apache.org/jira/browse/MJAVADOC-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17957478#comment-17957478
]
Olivier Lamy commented on MJAVADOC-61:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-javadoc-plugin#423|https://github.com/apache/maven-javadoc-plugin/issues/423].
> Adding custom source paths to javadoc
> -------------------------------------
>
> Key: MJAVADOC-61
> URL: https://issues.apache.org/jira/browse/MJAVADOC-61
> Project: Maven Javadoc Plugin (Moved to GitHub Issues)
> 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
> Assignee: Siveton Vincent
> Priority: Major
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
