[jira] Closed: (MJAVADOC-176) javadoc uses the undcoumented and platform unspecific -J-fullversion to determine version instead of the more standardized -J-version

["Vincent Siveton (JIRA)" <ji...@codehaus.org>]

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

Vincent Siveton closed MJAVADOC-176.
------------------------------------

         Assignee: Vincent Siveton
       Resolution: Fixed
    Fix Version/s: 2.4

Patch applied and snapshot deployed. Thanks!

> javadoc uses the undcoumented and platform unspecific -J-fullversion to determine version instead of the more standardized -J-version
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MJAVADOC-176
>                 URL: http://jira.codehaus.org/browse/MJAVADOC-176
>             Project: Maven 2.x Javadoc Plugin
>          Issue Type: Bug
>    Affects Versions: 2.3
>         Environment: All Platforms
>            Reporter: Alexander Sack
>            Assignee: Vincent Siveton
>             Fix For: 2.4
>
>         Attachments: MNG-176-maven-javadoc-plugin.patch
>
>
> The -J-fullversion is not as standardized as the -Jversion across multiple platforms.  On SCO UnixWare 7.1.4, the -J-fullversion returns the equivalent of the System's java.vm.version which has a non-standard string compared to the normal -J-version (the output you expect to be java version is "x.y.z_rev" etc.  Its wiser going forward to use just -J-version to determine the javadoc version number.

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