[ http://jira.codehaus.org/browse/MJAVADOC-61?page=comments#action_80635 ] Julien HENRY commented on MJAVADOC-61: --------------------------------------
I have a similar issue with source generated with antrun plugin. I have a multimodule project, and when I run mvn package -DperformRelease=true, the Javadoc of my generated source is generated and packaged, but when I run mvn site, I don't have the Javadoc of my generated class. Perhaps there is a problem with aggregate=true ? > 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
