[
https://issues.apache.org/jira/browse/MJAVADOC-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17957528#comment-17957528
]
Olivier Lamy commented on MJAVADOC-62:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-javadoc-plugin#516|https://github.com/apache/maven-javadoc-plugin/issues/516].
> javadoc:javadoc needs access to generated sources
> -------------------------------------------------
>
> Key: MJAVADOC-62
> URL: https://issues.apache.org/jira/browse/MJAVADOC-62
> Project: Maven Javadoc Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: John Dennis Casey
> Assignee: Siveton Vincent
> Priority: Blocker
> Fix For: 2.1
>
> Attachments: MJAVADOC-62.diff, MJAVADOC-62.diff
>
>
> currently, maven-model will not generate apidocs by simply calling
> javadoc:javadoc. This is because maven-model's sources are generated, and the
> javadoc report doesn't ensure that the 'generate-sources' phase is called.
> However, when I changed the report to have:
> @execute phase="generate-sources"
> It still doesn't work. I suspect this may be because it's forking a new
> lifecycle and cloning the project to call generate-sources, which means the
> report doesn't use the right project instance to create the report. However,
> I've been unable to inject ${executedProject} as a parameter; it fails the
> build, saying I need to supply that parameter on the command line.
> I haven't committed any code changes to this report, since I don't currently
> have time to debug it properly, and I obviously haven't solved the problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
