[ http://jira.codehaus.org/browse/MJAVADOC-4?page=all ]
Maria Odea Ching moved MNG-1237 to MJAVADOC-4:
----------------------------------------------
Version: (was: 2.0 (RC))
Fix Version: (was: 2.0.1)
Component: (was: maven-javadoc-plugin)
Workflow: jira (was: Maven)
Key: MJAVADOC-4 (was: MNG-1237)
Project: Maven 2.x Javadoc Plugin (was: Maven 2)
> Regression: javadoc plugin fails when a <maxmemory> parameter is provided
> -------------------------------------------------------------------------
>
> Key: MJAVADOC-4
> URL: http://jira.codehaus.org/browse/MJAVADOC-4
> Project: Maven 2.x Javadoc Plugin
> Type: Bug
> Environment: Windows XP
> Reporter: Martin Desruisseaux
> Assignee: Lester Ecarma
> 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 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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
