[
https://issues.apache.org/jira/browse/PROTON-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348316#comment-15348316
]
ASF GitHub Bot commented on PROTON-1224:
----------------------------------------
Github user gemmellr commented on the issue:
https://github.com/apache/qpid-proton/pull/75
you just need to ensure you have the upstream repo up to date, then rebase
your fork against it, then [force] push to your fork, which should result in
your commit(s) sitting at the head of the branch with the current upstream
commits preceding them and no unnecessary merge commits. You can repeat that
process as many times as you like.
You obviously want to avoid force pushes on branches you are using to
directly collaborate with other people on, but typically you commit work on a
specific branch for the PR and then since noone else is likely to be depending
on it doing such a force push is of little consequence to anyone.
> 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: [email protected]
For additional commands, e-mail: [email protected]
