You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Alexander Sack (JIRA)" <ji...@codehaus.org> on 2008/02/13 22:07:28 UTC

[jira] Closed: (MJAVADOC-177) javadoc should use -J-version to determine version, not -J-fullversion

     [ http://jira.codehaus.org/browse/MJAVADOC-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Sack closed MJAVADOC-177.
-----------------------------------

    Resolution: Duplicate

MJAVADOC-176, for some reason using Safari on Leopard, the JIRA workflow for creating a new issue causes a misleading error that made me believe the issue was not created.  After hitting Create, I got I couldn't BROWSE the 176 so I made 177 thinking it was pilot error.  Sorry about that.

> javadoc should use -J-version to determine version, not -J-fullversion
> ----------------------------------------------------------------------
>
>                 Key: MJAVADOC-177
>                 URL: http://jira.codehaus.org/browse/MJAVADOC-177
>             Project: Maven 2.x Javadoc Plugin
>          Issue Type: Bug
>    Affects Versions: 2.3
>         Environment: All platforms
>            Reporter: Alexander Sack
>            Priority: Minor
>
> Currently in JavadocUtil.getJavadocVersion(), we issue -J-fullversion to the javadoc binary to determine the version, e.g. 1.6, 1.5, 1.4 etc.  -J-fullversion is non-standard across platforms and Sun has already marked it as a hidden undocumented system property.  It would be more correct to use just -J-version which is ALWAYS defined on a Java enabled platform.

-- 
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