[
https://issues.apache.org/jira/browse/CRYPTO-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16988135#comment-16988135
]
James Baker edited comment on CRYPTO-143 at 12/4/19 7:37 PM:
-------------------------------------------------------------
Gary, thanks. It's sad that no release has happened because there's a _lot_ of
code on trunk that's unreleased (which presumably has never been used) and this
project does not appear to publish snapshots. In our case we fall back to slow
JCE if commons crypto fails to initialize for some reason and it was sad to
realise that we'd deoptimized ourselves by upgrading Ubuntu! Appreciate the
work of volunteers on this codebase and others - it's enabled a significant
performance improvement for us.
was (Author: jebaker):
Gary, thanks. It's sad that no release has happened because there's a _lot_ of
code on trunk that's unreleased (which presumably has never been used) and this
project does not appear to publish snapshots. In our case we fall back to slow
JCE if commons crypto fails to initialize for some reason and it was sad to
realise that we'd deoptimized ourselves by upgrading Ubuntu! Appreciate the
work of volunteers on this codebase and others.
> Release a new version to maven central
> --------------------------------------
>
> Key: CRYPTO-143
> URL: https://issues.apache.org/jira/browse/CRYPTO-143
> Project: Commons Crypto
> Issue Type: Task
> Reporter: Chris
> Priority: Major
>
> I've been maintaining my own fork of commons-crypto for over 2 years, shortly
> after forking someone merged the change I wanted into the master branch.
>
> It would be nice to no longer have to maintain or build my fork, or even
> build the master branch myself. There have been a number of fixes and
> enhancements in the last 2 years... Could we get a 1.0.1 release to maven
> central?
>
> Thanks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
