qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PROTON-1224) Proton-J SSL uses deprecated Bouncy Castle functionality
Date Fri, 17 Jun 2016 19:11:05 GMT

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

ASF GitHub Bot commented on PROTON-1224:
----------------------------------------

Github user JemDay commented on the issue:

    https://github.com/apache/qpid-proton/pull/75
  
    OK ... my lack of high-wire skills with GITis really showing through now ... i'm completely
stumped as to how to 'not' include other commits when pushing back to my fork ..



> Proton-J SSL uses deprecated Bouncy Castle functionality
> --------------------------------------------------------
>
>                 Key: PROTON-1224
>                 URL: https://issues.apache.org/jira/browse/PROTON-1224
>             Project: Qpid Proton
>          Issue Type: Improvement
>          Components: proton-j
>    Affects Versions: 0.12.2
>            Reporter: Jem Day
>
> The BouncyCastle project deprecated functionality used by the proton-j driver in version
1.48. This causes run-time issues for us as our application containers are using newer BC
versions.
> I've submitted a PR for this change and verified that all tests run using both BC 1.48
and 1.54.
> Note: The CI pipeline for the PR is flagging an error but i am able to build/test locally
with no reported errors - build log is attached to the PR comments.
> https://github.com/apache/qpid-proton/pull/74



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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message