You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Martin Desruisseaux (JIRA)" <ji...@codehaus.org> on 2005/10/19 06:48:11 UTC
[jira] Created: (MNG-1237) Regression: javadoc plugin fails when a parameter is provided
Regression: javadoc plugin fails when a <maxmemory> parameter is provided
-------------------------------------------------------------------------
Key: MNG-1237
URL: http://jira.codehaus.org/browse/MNG-1237
Project: Maven 2
Type: Bug
Components: maven-javadoc-plugin
Versions: 2.0 (RC)
Environment: Windows XP
Reporter: Martin Desruisseaux
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-1237) Regression: javadoc plugin fails when a parameter is provided
Posted by "Lester Ecarma (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1237?page=all ]
Lester Ecarma updated MNG-1237:
-------------------------------
Attachment: MNG-1237-maven-javadoc-plugin.patch
Please see attached patch for the fix.
> Regression: javadoc plugin fails when a <maxmemory> parameter is provided
> -------------------------------------------------------------------------
>
> Key: MNG-1237
> URL: http://jira.codehaus.org/browse/MNG-1237
> Project: Maven 2
> Type: Bug
> Components: maven-javadoc-plugin
> Versions: 2.0 (RC)
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MNG-1237) Regression: javadoc plugin fails when a parameter is provided
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1237?page=all ]
Brett Porter closed MNG-1237:
-----------------------------
Resolution: Fixed
Fix Version: 2.0.1
> Regression: javadoc plugin fails when a <maxmemory> parameter is provided
> -------------------------------------------------------------------------
>
> Key: MNG-1237
> URL: http://jira.codehaus.org/browse/MNG-1237
> Project: Maven 2
> Type: Bug
> Components: maven-javadoc-plugin
> Versions: 2.0 (RC)
> Environment: Windows XP
> Reporter: Martin Desruisseaux
> Assignee: Lester Ecarma
> Fix For: 2.0.1
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org