commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CRYPTO-104) Native code should provide getVersion() methods
Date Sun, 10 Jul 2016 23:49:10 GMT

     [ https://issues.apache.org/jira/browse/CRYPTO-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sebb resolved CRYPTO-104.
-------------------------
       Resolution: Fixed
    Fix Version/s: 1.0.0

CRYPTO-104 Native code should provide getVersion() methods

Project: http://git-wip-us.apache.org/repos/asf/commons-crypto/repo
Commit: http://git-wip-us.apache.org/repos/asf/commons-crypto/commit/eaed08d0
Tree: http://git-wip-us.apache.org/repos/asf/commons-crypto/tree/eaed08d0
Diff: http://git-wip-us.apache.org/repos/asf/commons-crypto/diff/eaed08d0



> Native code should provide getVersion() methods
> -----------------------------------------------
>
>                 Key: CRYPTO-104
>                 URL: https://issues.apache.org/jira/browse/CRYPTO-104
>             Project: Commons Crypto
>          Issue Type: New Feature
>            Reporter: Sebb
>             Fix For: 1.0.0
>
>
> It would be useful to have getVersion() methods for the native code.
> These should be able to return:
> - the VERSION used to create the library (i.e. project.version)
> - the NAME used to create the library (i.e. project.name)
> - the BUILD_DATE might also be useful
> - the OpenSSL version string
> - the SSLeay_version details
> Although the Java jar and the native code are generally built together, they are distributed
as separate files, so it's useful to be able to identify their versions independently at run-time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message