[
https://issues.apache.org/jira/browse/MJAVADOC-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17957376#comment-17957376
]
Olivier Lamy commented on MJAVADOC-4:
-------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[olamy/maven-javadoc-plugin#397|https://github.com/olamy/maven-javadoc-plugin/issues/397].
> Regression: javadoc plugin fails when a <maxmemory> parameter is provided
> -------------------------------------------------------------------------
>
> Key: MJAVADOC-4
> URL: https://issues.apache.org/jira/browse/MJAVADOC-4
> Project: Maven Javadoc Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Environment: Windows XP
> Reporter: Martin Desruisseaux
> Assignee: Lester T. Ecarma
> Priority: Major
> Attachments: MNG-1237-maven-javadoc-plugin.patch
>
>
> maven-javadoc-plugin fails when a <maxmemory> parameter is provided. This is
> a regression, since it was working in Maven 2 beta 3. This is caused by a
> change in the way parameters are handled in Maven 2 RC: the
> maven-javadoc-plugin now put them in an "options" file, and the command line
> now contains only:
> <path to j2se tools>/javadoc @options @files
> But the <maxmemory> maps to the -J-Xmx option, and all -J options are
> required to appear in the command line. They are not allowed to appear in the
> options file. See:
>
> http://java.sun.com/j2se/1.5.0/docs/tooldocs/windows/javadoc.html#argumentfiles
> maven-javadoc-plugin should put all -J options on the command line instead of
> the options file. This constraint applies at least to the following
> parameters:
> <maxmemory>
> <minmemory>
> (I have not checked if it applied to other parameters).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
