[
https://issues.apache.org/jira/browse/CODEC-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16873279#comment-16873279
]
Benjamin Asbach edited comment on CODEC-55 at 6/26/19 12:11 PM:
----------------------------------------------------------------
We also stumbled over this issue since a "Security Vulnerability" was raised by
WhiteSource. The support refused a removal "for the reason that some of our
customer insisted on it beeing present". Which from my point of view is quite
weired.
Maybe [~ggregory] could close this bug as "won't fix" or "not a bug". Perhaps
afterwards they're willing to remove their finding (WS-2009-0001).
If you're also affected by this finding you may reach out the WhiteSource
support too.
was (Author: asbachb):
We also stumbled over this issue since a "Security Vulnerability" was raised by
WhiteSource. The WhiteSource refused a removal "for the reason that some of our
customer insisted on it beeing present". Which from my point of view is quite
weired.
Maybe [~ggregory] could close this bug as "won't fix" or "not a bug". Perhaps
afterwards they're willing to remove their finding (WS-2009-0001).
If you're also affected by this finding you may reach out the WhiteSource
support too.
> make all "business" method implementations of public API thread safe
> ---------------------------------------------------------------------
>
> Key: CODEC-55
> URL: https://issues.apache.org/jira/browse/CODEC-55
> Project: Commons Codec
> Issue Type: Wish
> Reporter: Qingtian Wang
> Priority: Major
> Fix For: 1.x
>
> Attachments: CODEC-55-Wrapper-Implementations.patch,
> concurrentCodecs.diff, concurrentQDiff.diff, urlcodec.patch
>
>
> Maybe most of the implementations are already thread safe. Just such that
> codec can say so in general...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
