maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Sack (JIRA)" <j...@codehaus.org>
Subject [jira] Created: (MJAVADOC-176) javadoc uses the undcoumented and platform unspecific -J-fullversion to determine version instead of the more standardized -J-version
Date Wed, 13 Feb 2008 21:01:28 GMT
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


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

        

Mime
View raw message