commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CRYPTO-109) Move Openssl JNA to feature branch
Date Wed, 06 Jul 2016 10:10:11 GMT

    [ https://issues.apache.org/jira/browse/CRYPTO-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364083#comment-15364083
] 

Sebb commented on CRYPTO-109:
-----------------------------

It's easy enough to avoid the JVM crash. However the obvious fix entails not deallocating
the context.
If this is acceptable, then I would prefer to leave the code in place so we can potentially
get some feedback.
The implementation is not currently included in the factory enums, and is not a default, so
users have to specifically request it.

The first release will be at most a beta release as the JNI code does not build on Windows
(and possibly other systems), so I don't see the harm provided it is made clear that the JNA
implementation is alpha quality.

> Move Openssl JNA to feature branch
> ----------------------------------
>
>                 Key: CRYPTO-109
>                 URL: https://issues.apache.org/jira/browse/CRYPTO-109
>             Project: Commons Crypto
>          Issue Type: Bug
>            Reporter: Dapeng Sun
>            Assignee: Dapeng Sun
>
> JNA is an important feature.
> Since it have some bugs like causing JVM crash, the target of JNA should be next release(after
1.0.0). We should move the related code to feature branch currently.
> If JNA feature is strong demanded, we can speed up the progress of merging JNA feature
branch to master and make another release.



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

Mime
View raw message